Thanks for your response. Actually I have looked at some of them, although not in great detail and haven't actually installed them. I do have to do some more investigating, but I think I can say something right now. The one thing I think I have to offer in terms of originality is the idea of keeping state of record selection, and making that selection affect (filter) the listing of related tables.
As an example this is the way a master-detail application for a chain of book stores works normally: There is a detail form with a list of stores, and upon selection of one of them, the id of the store is passed as a parameter to a new page which lists the books in that store. In my version, there is also a detail form with a list of the stores, but the store id is not passed as a parameter, it is saved as a session variable. Upon loading the page with the list of books, a filter takes effect taking into accoung the store id. The saving of the session variable and the filtering is never specified though. It is done automatically given the existence of a foreign key in the books table making reference to a store id. As far as I know, db object relational mapper systems take care of the creation of the tables in the actual database, and are capable of generating forms given a table name, but my system would also take care of the selection of records, and the cascading effect that has on related tables in the sense of how they are listed in detail forms with corresponding filters. I'm not sure that it is that new of an idea, or that helpful from someone else's point of view, but it is something that I have put into practice and have a good concept of it. And I do recognize I should do more investigating... Graham Dumpleton-2 wrote: > > On Sep 6, 9:32 am, rieh25 <[EMAIL PROTECTED]> wrote: >> Is it such a bad idea that it doesn't deserve a reply? > > You only posted the question six hours ago. Maybe the people who might > want to comment are asleep. > > BTW, have you done an analysis of the various existing database object > relational mapper systems for Python that already exist? There are > also some systems for automatic web application forms generation based > on database data as well. > > How is what you have in mind different to or not covered by these > existing packages? > > If you describe how what you want to do isn't satisfied by the > existing systems then people may be more interested in commenting. If > you aren't aware of these existing systems then perhaps use Google to > do some research on them first. > > Graham > >> rieh25 wrote: >> >> > I've been thinking about a module (actually I have it partially >> > implemented in Zope), that would do the following things: >> >> > - Read the structure of a MySql database (fill a dictionary with it) >> >> > In order to: >> >> > - Quickly create detail/filter/update forms given a table name (without >> > specifying the fields because they have already been detected) >> > - Keep state of record selection. In order to implement Master-Detail >> form >> > processing, with unlimited levels of parent-child table relations, >> which >> > have also been detected already (foreign keys) >> > - Management of interrelation between security and menus (a user can >> only >> > access certain parts of the application) >> >> > I think that Ruby on Rails does something similar, but still I thing it >> > would be interesting to implement it in Python. What do you think? >> >> -- >> View this message in >> context:http://www.nabble.com/Module-for-mod_python-tf4386823.html#a12513012 >> Sent from the Python - python-list mailing list archive at Nabble.com. > > > -- > http://mail.python.org/mailman/listinfo/python-list > > -- View this message in context: http://www.nabble.com/Module-for-mod_python-tf4386823.html#a12514597 Sent from the Python - python-list mailing list archive at Nabble.com. -- http://mail.python.org/mailman/listinfo/python-list
