This sounds like a bug. I'm guessing that you mean the object's primary key field isn't updated after save, correct? According to the docs:
http://download-east.oracle.com/docs/cd/B19306_01/java.102/b14355/jdbcvers.htm#CHDEGDHJ Oracle's driver should support auto-generated keys, which is what we use in Mapper. Can you confirm that what I'm saying is what you're seeing? Thanks, Derek On Mon, Mar 2, 2009 at 8:56 AM, radoslaw.holewa <[email protected]>wrote: > > On 20 Lut, 01:50, Debby Meredith <[email protected]> wrote: > > Folks, > > > > We're looking for some most excellent people to volunteer to test the > > Oracle 10g JDBC driver in lift-mapper as soon as possible. Any hands > > going up out there? Perhaps Greg Meredith, who has a wonderful last > > name if I do say so myself, would like to sign up? Anyone else? > > > > Thanks in advance! > > Hi, > > I'm using Lift mapper in one of my projects and my database is Oracle > 10g. > Unfortunately I have some problems with primary keys. After I save my > object > it's primary key is not set. > I tested it with MySQL and H2 database and everything went well. > So, my question is: do you have any solution for setting primary key > after object is saved? > Of course using oracle database :) > > Cheers, > Radek > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
