[Lift] Re: Two database are broken in 1.1-M8, works fine in 1.1-M7 .

2010-01-13 Thread Neil.Lv
David, Thank you very much! It works now, I'm so sorry about that I didn't see the yak demo yesterday . :) Cheers, Neil On Jan 14, 12:43 pm, David Pollak wrote: > On Wed, Jan 13, 2010 at 6:18 AM, Neil.Lv wrote: > > Hi David, > > > I'm sorry about it that i write it wrong. > > > Bu

Re: [Lift] Re: Two database are broken in 1.1-M8, works fine in 1.1-M7 .

2010-01-13 Thread David Pollak
On Wed, Jan 13, 2010 at 6:18 AM, Neil.Lv wrote: > Hi David, > > I'm sorry about it that i write it wrong. > > But I change the second DBVendor name to DBVendor_2, and it create > a db file named "lift_proto2.db.h2.db". > And it doesn't work, I add this method to the User model to specify > th

[Lift] Re: Two database are broken in 1.1-M8, works fine in 1.1-M7 .

2010-01-13 Thread Neil.Lv
Hi David, I'm sorry about it that i write it wrong. But I change the second DBVendor name to DBVendor_2, and it create a db file named "lift_proto2.db.h2.db". And it doesn't work, I add this method to the User model to specify the default db connection. ### override def dbDefaultConnection

[Lift] Re: Two database are broken in 1.1-M8, works fine in 1.1-M7 .

2010-01-12 Thread David Pollak
The problem with this code is you are using the same connection vendor for both connection identifiers *and* you're not defining a vendor for the DefaultConnectionIdentifier On Jan 11, 7:05 am, "Neil.Lv" wrote: > Hi all, > >    There is a problem when i upgrading the 1.1-M7 to 1.1-M8, the db > co