Thanks! I'll give it a go and see what happens. :-) On Sunday, January 5, 2014 1:02:52 PM UTC, Niphlod wrote: > > > > On Sunday, January 5, 2014 1:57:24 PM UTC+1, pythonic...@gmail.com wrote: >> >> 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? >> > > sure, but don't expect being able to use something like db.table(5) as a > shortcut 'cause the missing PK. selecting with the "usual" > db(db.table.field == 'something').select() will work out of the box, unless > your fields have some really strange names, but those can be circumvented. > > >> >> 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. >> >> > yep, you can have as much dbs as you like. > > db0 = DAL(....) > db1 = DAL(....) > db2 = DAL(....) > > etc etc etc >
-- 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.
