There was some chatter about a month ago about some issues running Doctrine 1.1 with sf 1.2 (I can't find the topic at the mo and I can remember what the issues were). In the url you posted there should be a link to a trac ticket - which you'll need to checkout for some additional changes you'll need to implement.
jw probably has a better idea of the issues than anybody - so he might chip in with some tips if he has the time. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Johannes Heinen Sent: 19 May 2009 10:40 To: symfony users Subject: [symfony-users] Re: sfDoctrinePlugin/sf1.2 Hey again, i've found this link: 2 lines to migrate the new doctrine 1.1 version into the sf 1.2 release. Perhaps somebody considers it helpful. http://www.symfony-project.org/blog/2009/01/12/call-the-expert-using-a-custo m-version-of-doctrine So my previous comment seems to be obsolete (as most times^^ ;)). I'll try it out and write a line on how it worked. Thanks :) On May 19, 10:31 am, Johannes Heinen <[email protected]> wrote: > hey:) > Sorry for the confusion: I've found out that the doctrine plugin > shipped with symfony 1.2 is based on the 1.0 release of doctrine - as > you already said it - i had read this small, but important notice > recently in the doctrine 1.1 release notes:http://www.doctrine-project.org/blog/doctrine-1-1-released. > > And you are right: This release does not log the changes made on a > Doctrine_Record instance yet :( So my provided solution *will not > work* for the current symfony release. > > Hopefully the new doctrine release will be patched into the sf 1.2 > plugin, but as you can read in the doctrine's release notes: it seems > even not to be clear if the new version will be shipped with the sf > 1.3 final. :( > > Damn, but I need this stuff ^^ > > Thanks, > Joshi > > On May 19, 9:53 am, "David Ashwood" <[email protected]> > wrote: > > > It exists also in the 1.0 version Doctrine that comes with Symfony 1.2 :) > > Watch out though - It'll only work with the current record - with Doctrine > > 1.1 you can also optionally check child records. > > > -----Original Message----- > > From: [email protected] [mailto:[email protected]] > > > On Behalf Of Johannes Heinen > > Sent: 19 May 2009 00:17 > > To: symfony users > > Subject: [symfony-users] Re: sfDoctrinePlugin/sf1.2 > > > whoho, got it. For the ones who want to know: > > >http://www.doctrine-project.org/documentation/manual/1_1/en/component... > > ew > > > getModified(true) is the keyword. > > > thanks. > > > On 18 Mai, 18:17, Johannes Heinen <[email protected]> > > wrote: > > > HI all, > > > > is there a way to revert changes made to an doctrine object during a > > > transaction? > > > > I user the preSave() Hook to do some stuff and set attributes > > > depending on their original values. I don't see any way to retrieve > > > these original values, i'd only found methods to retrieve information > > > about which columns have changed. > > > > Is there a method like (getOriginalValueForField('myField')) ? > > > > Thanks, > > > Johannes --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" 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/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
