[PyQt] postgresql

[Erik Janssens]

Indeed the model/view/delegate framework is very flexible and remains
snappy, even when displaying POPO's.  The advantage of using an orm is that
you can display properties of your objects, along with attributes.

sqlalchemy / elixir is a very flexible framework that makes using complex
queries easier (not easy).

you could use the Camelot framework to avoid writing boilerplate code to
map you python objects to tables.  some screenshots are available at :
http://www.conceptive.be/projects/camelot/wiki/ScreenShots

2009/3/19 Damien Elmes <resolve at ichi2.net>

> >> So an alternative would be to reimplement the Qsql classes using
> >> based on the Python DBAPI protocol, but maybe the cost/benefit ratio
> >> for that is too high?
> > I'd say far to high. Qt has it own philosophy with databases, if you want
> > snappy grids, and automatic updates and all that stuff, i'd suggest to
> stick
> > to PyQt4 cplusplus-ish way of dealing with data. It's not pythoninc but
> it
> > works quite well. I must admit ORM's are much more nice to work with, but
> SQL
> > is not so bad.
>
> You don't need to use Qt's SQL support for snappy grids and automatic
> updates. Qt's model/view architecture is quite flexible and I achieve
> very good performance with sqlalchemy (bypassing the ORM) and a custom
> table model. It wasn't hard to write, either - but it is more work
> than using Qt's premade SQL model.
> _______________________________________________
> PyQt mailing list    PyQt at riverbankcomputing.com
> http://www.riverbankcomputing.com/mailman/listinfo/pyqt
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.riverbankcomputing.com/pipermail/pyqt/attachments/20090319/ed0d6095/attachment.html