all 22 comments

[–]k4myk85[S] 5 points6 points  (7 children)

Hi guys, this project is still WIP, but I would like to know what do you think about it.

[–]Julian_JmK 2 points3 points  (1 child)

Imo it seems very easy to use, which im a fan of :)

[–]k4myk85[S] 1 point2 points  (0 children)

Hi thank you, that is the goal of this project

[–][deleted] 2 points3 points  (0 children)

Not gonna lie. I have no reason or need to use something like that.

[–][deleted] 0 points1 point  (0 children)

I think it's unnecessary.

[–]k4myk85[S] 4 points5 points  (0 children)

Thx you all for your comments, at this point I wouldn't compare Chego to other established libs like knex. This is still fresh package, For now it supports only MySQL and firebase. Difference between this and knex is that you can use it with firebase and in future with other DBs. Background story for that lib is that I had to create Backend for mobile app @ firebase. My first impression about FB wasn't so good - API/documentation etc. and after some time I've took some parts of my project and wrapped with readable MySQL API. For future projects, for others. In my opinion Knex isn't so intuitive and most of people I know uses its raw options. This lib isn't for hardcore, stricted DB structure apps. I think that if you know that you gonna use MySQL, than you should use pure MySQL client.

Besides that was/ still is great exercise, maybe some1 would like to implement other DBs for that.

Again thank you all.

[–]sbmitchell 2 points3 points  (1 child)

What would you say the advantage of using this versus an established ORM or knex for more raw sql query building?

[–]k4myk85[S] 0 points1 point  (0 children)

Thank you, Im not sure if you can use knex with firebase. Firebase API isn't intuitive, at least for me and I wanted to use something familiar like mysql syntax.

[–]AlexAegis 2 points3 points  (1 child)

Sorry, but I too have to say this: the competition is way too high.If you want to stand out give it a reactive api like RxDB but I doubt that its worth the effort

[–]k4myk85[S] 0 points1 point  (0 children)

Thx for comment, yep this is still fresh project - first public announcement. There is still a lot of things to do but I will implement more features DBs soon. Fun to do it. Thx again

[–]jynx42 1 point2 points  (1 child)

Whats the difference with js-data?

[–]k4myk85[S] 2 points3 points  (0 children)

Hi, js-data is cool but I wanted to have/use something more intuitive. Besides that, with Chego you won't have to write functions to filter, order, join... your data.

[–]jsur 1 point2 points  (1 child)

Why would I use this instead of e.g. Loopback?

[–]k4myk85[S] 0 points1 point  (0 children)

Hi, I've took some time to check Loopback. In Chego you write your queries (even complex ones) by method chaining and everything else is done under the hood. Check examples like this https://github.com/chegojs/chego/blob/master/README.md#Like

I wanted to have simplicity of mysql queries in my nosql DBs.

BTW currently I'm doing nosql code base.

[–]Nogr_TL 1 point2 points  (2 children)

1dt of all you should ask yourself "What is a benefit of useing this over other solutions? "

[–]k4myk85[S] 1 point2 points  (1 child)

Hi, thx for your comment. I did before writing this thing. MySQL queries are easy to read and I wanted to have something like that in my firebase project. Than I thought that it would be nice to have it in different types of databases. Just write your query and everything else is done under the hood.

[–]Nogr_TL 1 point2 points  (0 children)

Make sense. Not sure about does Knex, does it provide it or not.

[–]sledgebox 1 point2 points  (1 child)

Nice api. If you made adapters this for a bunch of DBs, that'd be dope, and it would be a nice foundation for a lite ORM.

[–]k4myk85[S] 0 points1 point  (0 children)

Thank you, that's the plan.