Thanks. That allows me to narrow it down to two questions: 1) I'm just going to want to use various select queries against views/tables (including joins) in the "legacy" database, nothing else. This database will never need to be altered by web2py. Will I be able to do that?
2) If I want to do want to write anything, I guess web2py will let me have a separate native database which I can use for that. You can have multiple databases right? A mix for native and legacy? Neither will need to interact directly with the other and the logical separation would be well suited to this application. Cheers. On Sunday, January 5, 2014 9:44:30 AM UTC, Niphlod wrote: > > "legacy" db are the ones that were not created in web2py applications. > The concept behind is that you can still query whatever database you want > just using db.define_table(......, migrate=False). > That being said, without an auto-incrementing column or a PK you'd loose > quite a bit of DAL features/shortcuts. It's hard to tell if you're going to > face those limitations without knowing what you want to do with those > databases. > > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
