Re: Yet another database question, please

From: Bruno Desthuilliers <bruno.42.desthuilliers@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 30 Nov 2007 14:47:46 +0100

nmp a écrit :

Hello to all. I am only just learning both Python and PyGTK (with Glade). I also need to learn how to use databases in my programs. My preliminary research leads me in the direction of SQLAlchemy, which seems to be what everybody else is using.

Since it's not quite clear from your question: SQLAlchemy is a pretty good package, but you need still need to know SQL to use it effectively (if it's your case, please forget this remark).

So, does anyone have a good example that shows how to tie these things toegether? I would like to have the GUI dialogs and treeviews directly interacting with the underlying tables and/or views.

[cough]Like Borland Delphi 1.0, in the nineties...[/cough]

From experience (with Delphi, VB and a couple related but less known systems), directly tying widgets to database is a pretty brittle architecture for anything else than Q&D Simple Stupid GUI/DB pipelines.

.

Prev by Date: Re: Oh no, my code is being published ... help!
Next by Date: Gnu/Linux dialogue boxes in python
Previous by thread: ANN: A Primer on Python for Life Science Researchers
Next by thread: Re: Yet another database question, please
Index(es):
- Date
- Thread

Relevant Pages

Re: A question on decorators
... some of the databases and tables I access are being accessed by other ... SQLAlchemy or SQLObject, because I didn't want too (although in the ... the OP is looking for the PersistentDict and PersistentList ... Python module would have to allocate from the ROM, ...
(comp.lang.python)
Re: Yet another database question, please
... I also need to learn how to use databases in my programs. ... From experience (with Delphi, VB and a couple related but less known ... and the higher-level SQLAlchemy package. ...
(comp.lang.python)
Re: A question on decorators
... some of the databases and tables I access are being accessed by other ... SQLAlchemy or SQLObject, because I didn't want too (although in the ... I'm not sure that triggering a database write for each and every modified attribute is a good thing; I'd use a "dirty" flag instead and write all modifications at the end. ... Since not all methods modify the object contents, using a metaclass to flag all of them isn't a good idea either. ...
(comp.lang.python)