For the majority of objects in our db's we have a set of standard fields: tablenameKey (surrogate primary key) Ref (a user Id or transaction Id or something along those lines) Status Create date Create user Create application Update date Update user Update application Delete date Delete user Delete application
Every major table contains these fields, sorted alphabetically amongst the other needed data for the table. I have been through the docs quickly and I am several pages into actually working through the examples and I don't see any to inherit this sort of behavior. Have I missed something? Also I have a question about organizing large numbers of tables. In the zblog example there is a file for tables, individual files for the classes that are actually used and a file that contains the mappers that also set up the get by functions in the classes that they map to. This looks like it would work for probably up to twenty tables. Does it make more sense to just put the class, the table and the mapper all in the same file, one for an entity? Thanks for the help, It looks like SA is going to fill in some gaps for me. -- *********************************** See there, that wasn't so bad. *********************************** Johan Wolfgang von Goethe said, "Treat people as if they were what they ought to be, and you help them to become what they are capable of being." I kind of like that. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ Sqlalchemy-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
