Is this a string field or a numeric field? It sounds like the type defined in the Transfer config is not the correct type?
Aside from that, I'm having a hard time understanding why anyone would use a value like this as a primary key. If two records are created at the same time, what happens? One just throws an error? If you have control of the schema, can you change it to an autoincrementing id or at least a UUID? This sounds like it's going to turn into a nightmare later. On Mon, Mar 2, 2009 at 5:20 PM, Chris Woerz <[email protected]> wrote: > > I have a table with a primary key that based on the datetime at record > creation (ie 20090226114107) recently when i invoke save() i get an > error because the primary key that transfer tries to insert is > '2.0090226114107E13'. is there anyway to resolve this? im pretty new > to transfer and i inherited an app that im not sure was setup > correctly. > > > > --~--~---------~--~----~------------~-------~--~----~ Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups "transfer-dev" 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/transfer-dev?hl=en -~----------~----~----~----~------~----~------~--~---
