4 ms·
yes, and Qt SQL does one thing and does it well, which is getting SQL data in a format compatible with Qt's data model. You can do it by hand but you will just
by jcelerier 4y ago
yes, and Qt SQL does one thing and does it well, which is getting SQL data in a format compatible with Qt's data model. You can do it by hand but you will just literally be reimplementing what is in QtSQL's module as soon as you want to display the result of queries in a table in your GUI. Same for scripting: the "meta and introspection facilities of Qt" are exactly what makes it possible to just call a member function or set a property of a C++ object from QJSEngine ; you can use another JS engine but you'll just end up reimplement all the glue code that is in QJSEngine, and for the sake of what? Having DLLs that start with another letter than Q?
- Rochus 4y ago> and Qt SQL does one thing and does it well Well, that's not particularly what the Unix philosophy is up to, unless Qt Sql is a separate project. > use another JS engine but you'll just end up reimplement all the glue code that is in QJSEngine There is no necessity to have it in the same project. And there is still original Qt if you want to have it all.
- jcelerier 4y agoI don't understand why being in the same or a separate project matters at all. It's an entirely theoretical thing. The only actual meaningful question is if it is in the same shared library or not (and it isn't). Your CPU does not care that function A comes from company A and function B from company A or B when executing, it'll be the same code.