Are you using some kind of shared or persistent DataContext when the user
logs in, but using a temporary or throw-away DataContext when you perform an
update? The shared one would load the data once the first time it was
accessed, but the changes to the temporary one might not be set to propagate
back to that shared one.
-Mike
Fredrik Liden <flide..ranslate.com> wrote:
> I'm getting a weird caching error.
>
> One user logs in, updates data on an edit page, submits and everything
> looks ok on the view page.
> At this point I looked in the database and the new values are indeed
> there.
>
> BUT, then when the user logs out (and kills the session) and then logs
> back in again, the view and edit page displays values that are old. Way
> old.
>
> Does anyone have any ideas what's going on?
> If I refetch the object every time I view it the error doesn't occur.
> But it's a lot of information to be loaded over and over. So I prefer
> not having to refetch it so often.
> Are there other errors than validation errors that I need to check for
> while doing the commit? But then why is the database updated but not the
> context, it seems that once the user logs in the dataObject uses some
> old data that was stored in the context.
>
> If anyone has any input I'd be thankful
>
> Fredrik
>
>
>
>
> -----Original Message-----
> From: Fredrik Liden
> Sent: Wednesday, April 20, 2005 5:36 PM
> To: cayenne-use..bjectstyle.org
> Subject: Ordering of fields
>
>
> Does the order of the dbfields in the Map.xml have to be the same order
> as the fields appear in the actual database table? I'm getting some
> strange errors.
>
> Thanks,
> Fredrik
This archive was generated by hypermail 2.0.0 : Wed Apr 20 2005 - 22:37:10 EDT