I’ll rephrase: I am wondering what will be knex?
LOL…I was slow there.
Actually the Database Creator is driven by Knex Migrations, so everything you do is saved as migration file that you can apply or rollback and later fully apply on your production server!
That’s great to know! Will it include seeding for app db settings and all that stuff?
Also, for the loooong future, will we be able to create models, validations and relations based on some custom Wappler ORM based on knex? I know that requires a huge redesign of the framework but it would be essential to keep progressing in the nocode direction.
I just can imagine people querying the database by using the new tag system you guys implemented recently. Very similar to Bubble but without all those restrictions and caveats that come with Bubble(which are many).
BTW, don’t you hate when you sneak peak a feature you have been working so hard on and are eager to deliver and then b*st!rds like me start to ask when are you going to send rockets to Mars?
So coming back to reality and today. The UI looks sleek I am eager to start using migrations(and seeding if possible)
Well, this certainly looks interesting. Will it replace my Navicat workflow? We’ll see.
Mmm, how bout some ObjectionJS knex?
See what I did there? Haha!
I’m curious about this too. It will very convenient to have access to and manage the database schema from within Wappler, but I would hardly expect it to have all the features of Navicat. I expect the best solution will be to use both, but most of the time it won’t be necessary to open up Navicat. I’m really looking forward to seeing it.
that’s real porn for wappler user !
Very cool @George… hoping for some mobile enhancements too!
Edit: Or you don’t need migrations of course. For me it’s the most interesting feature
I don’t think I would be happy skipping Navicat. It has so many useful features. I’m not sure what it doesn’t have that I would need. To update local > remote tables I’m developing, I usually simpy copy/paste but I could synchronise the structure (or data). I don’t think Navicat would allow you to rollback changes, but before I make changes I usually make a backup just as easily as if I would backup a PHP file before making changes.
I suppose Wappler won’t be able to keep track of the changes if they’re not done within Wappler - perhaps that’s the issue. I hope it will still be possible to use the new feature, but if not, never mind.
I feel the same, I’m a HeidiSQL user, it’s very powerful and very well developed so I really can’t ever see Wappler being a replacement for it. However, I can see Wappler drastically cutting down the amount of time I spend switching between the two, this is great for my workflow and will save a considerable amount of time for everything I do within Wappler.
Edit: I sat down and thought a bit more about this, I’m not a power user for HeidiSQL so it may be entirely possible that Wappler could catch up to HeidiSQL regarding how I use it, if it ever manages to do that it would make a huge difference to my time/workflow combo.
Can’t wait to see it all in action - thanks again TeamWappler for an excellent product!
I think the biggest advantage will be for people who’ve never had much to do with databases (i.e. why a lot of people use something like Bubble). This will be a game changer for them (and maybe myself included but I’ve finally settled on Navicat and getting the hang of that)
In that aspect the current iteration will not be as newbie friendly as Bubble. Bubble uses an ORM to power their database.
And while it falls short when you are a power user it is very helpful for newbies. They have custom types like date ranges which are built using whatever ORM they use. You don’t have to worry about relations as they are also built-in.
I think that the first iteration of Wappler’s DB creator will be schema/data management and migrations. But they will not stop there. I know they discarded existing ORMs like objection or bookshelf, but I believe they will create their own eventually. That’s why they chose knex.js which is what objection and bookshelf use as a base.
@George, access to my production database will only be through an SSH tunnel… it would be great if that was part of the setup too!