sounds easy enough then :) I think I equated something I configured wrong to something not supported. SO, will do the second connection as you suggest.
Thanks for the reply :) Mart On Nov 14, 6:28 am, Nico de Groot <[email protected]> wrote: > Hi Mart, > > No problem, you can define a second connection, say db_ms, that > connects to your ms sql database. And then query and insert across > databases. > > Nico > > On 14 nov, 07:30, mart <[email protected]> wrote: > > > Hi, > > > So, application "build system" uses SQLite for most current and future > > software builds. But would also like the application to connect to an > > MSSQL which which hosts legacy software builds. The legacy builds will > > continue to be used and even updated for some time, so daily updates > > would need to be caught as well. SO, the requirement is to build the > > older builds with the new build systems, but without changing anything > > on the older legacy side. > > > Suggestions? Would I be able with web2py to do some context switching? > > I.e query MSSQL DB, grab some data, then store that in the newly > > generated tables of an SQLite db, then begin as normal. > > > Or, i'm thinking it would be better to replicate/convert the MSSQL DB > > to SQLite (with daily updates) Would the DAL support that kind of > > activity ? The optimal scenario is that the the build system owns that > > activity which use the DAL with web2py ad also as Stand ALone > > > Again, any help or direction would be much appreciated. > > > Thanks > > Mart :) > >
