[Qt5-feedback] ORM in Qt5 ?

[Andre Somers]

Hi,

Op Do, 12 mei, 2011 11:54 am, schreef daniel.molkentin at nokia.com:
> Hi Frederic (and others),
>
> a lot of features proposed either here or in the blog comments is
> functionality that could be added at any time. One example is a ORM
> library. I can be added at a later point in time (Qt 5.1).
>
> Also, most probably a lot of requests won't be implemented by Nokia, but
> rather someone else.
> This is something to get used to. Traditionally new releases have
> triggered the same kind of requests, because only the trolls could get
> features in. Please think twice.
>
> There is no need to rush things into the .0 release. If you would like to
> see a certain feature, draft it, develop it, and contribute it (you will
> soon be able to).
>
> We should rather concentrate on core design issues that you need to get
> right for b/c reasons. After 5.0 is out (and I agree we should move on
> quickly, to not have a long gap after 4.8 and to avoid the temptation of
> serious breakage), we should Release Early, Release Often (tm), and get
> new features in along the way.

All true, but at the same time I think it is the right moment to think
about the question if Qt needs some kind of data framework, what the
needed features of such a thing would be, and what would be needed to
realize it. If a conclusion is reached that in order to realize such a
thing, non-bc changes to existing classes are needed, then waiting with
this discussion until after the introduction of Qt 5.0 is pushing this
functionality back to 6.0.

I think it _would_ be good to think about such a framework. I think it
would be very important to have. It should not only work on top of QtSQL,
but should, IMHO, have a *much* broader scope. It should be able to work
on top of different back-ends (QtSQL, but also local or remote files in
XML or binary formats, as well as web services for instance). It should be
asynchronous (as opposed to the current QtSQL stuff) to make it work
smoothly for bigger data sets and/or for data sources that suffer from
high latency.

Such a thing is not a trivial beast, but it could have a huge impact on Qt
I think. I am not sure it can be realized in an elegant way by gluing it
on to an existing Qt version. The answer may be that it can, but it would
be good to think about it.

André

>
> On May 12, 2011, at 11:18 , ext Frédéric Meurou wrote:
>
>> Hi,
>>
>> I've been playing with QtSql and IMHO, the SQL layer is suboptimal,
>> either in querying the database, and in being integrated in a app :
>> - from what i've seen, queries should be constructed using JOINs.
>> - from an integration point of view, dealing with foreign keys is a real
>> pain. Although QSqlRelationalTable helps when it comes to displaying
>> information, fetching data across tables using foreing keys requires a
>> lot of overhead.
>> I've used the Django ORM, and it really lessens the dev time.
>> I know there are few Qt ORM projects out there, it would be great to
>> integrate the in the QtSql module.
>>
>> Regards,
>>
>> Fred
>>
>> _______________________________________________
>> Qt5-feedback mailing list
>> Qt5-feedback at qt.nokia.com
>> http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
>
> _______________________________________________
> Qt5-feedback mailing list
> Qt5-feedback at qt.nokia.com
> http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
>