On Dec 19, 4:32 pm, DenesL <[email protected]> wrote: > you have to keep the definitions in logical sequence, for > example: > in db1 (and only in db1) you would define db=SQLDB(...) > in db2 you could do your define_tables > in db3 your requires > so that the objects have been defined when you are trying to use them.
OK, this works if I keep a single database :) This gets me most of where I need - each module can have an independent file for it's tables & requires/represent/labels/comments - as long as linked tables get loaded by earlier modules...as you say... It doesn't work for creating more than 1 database, though, which seems a shame. This might give better performance? (to be tested) It makes the namespaces nicer if each module has it's own database: module.table.field instead of: db.module_table.field Not too big a deal, though - I get my main aim :) Thanks a lot, Fran. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
