On Tuesday 09 January 2007 07:08, sheila miguez wrote: > On 1/9/07, Ed Leafe <[EMAIL PROTECTED]> wrote: > > On Jan 9, 2007, at 3:37 AM, Carl Karsten wrote: > > > also, I think your code has a bug: the database name wasn't being > > > used. so I > > > think if there was the same table name in two different db's, it > > > would ... > > > something bad. i fixed that, but with a hack. I couldn't figure > > > out how to get > > > the db name from the connection. > > > > The connection is to a specific database, right? Why do you think > > that it would suddenly decide to connect to some other database? Did > > you find a case where this actually happened? > > I do this. I use dbvis to connect to multiple databases while > debugging. We also write to more than one database while making a > booking so it is also a use case in our code, not just dbvis's. We > consume and produce a lot of data. > > Most recent debugging was to try and figure out why an itinerary code > was getting stored in one database but not the other. The field name > is the same.
Is this a case where more than one instance of the database engine is required. Because I know of no database engine that allows the dup's of the database name within the same instance of the database engine. Of course you can have database names "dbOne" and "dbTwo" that can have tables with the same name. But then dabo would require two connections. One to "dbOne" and a second to "dbTwo". This contrived situation does happen often and should be addressed. But the wizard does not deal with the problem in anyway. Bottom line this would have to be hand coded to create the second connection. Still Dabo passes the database name to dbMsSQL.py to create the connection. -- John Fabiani _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
