Hello, by reading the source code I think you should try try saving the object and then issuing $object->setPrimaryKey(6); and then save again. I did not dig more to see if that would work but give it a try. Also, I woul try setting defaultIdMethod="none" in your schema file (at the very top, it is not most probably set to "native").
Hope that helps. Kiril On Sat, Nov 1, 2008 at 11:33 PM, Vincent Lemaire <[EMAIL PROTECTED]> wrote: > > Hi, > > I have a problem with Symfony 1.1 and Propel 1.2. In fact, I make an > data load from an old application not made by Symfony and I want to > keep old data's primary keys but it doesn't works! > > I use setId() and setPrimaryKey() but Propel automatically > recalculates the primary key when primary key have been deleted. For > exemple, if I make $user->setId(6) or $user->setPrimaryKey(6) and the > id "5" does not exist, the line is registered under the id "5". It's a > big problem for me because it break my foreign keys! I made a > var_dump($user) before saving and ["id:protected"] has the value > int(6) but, after saving, $user->getId() returns "5"! > > All is up-to-date in the trunk of sf 1.1. > > Have you an idea? > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
