construct + autoupdate(0)

[prev] [thread] [next] [Date index for 2005/05/13]

From: Christopher Laco
Subject: construct + autoupdate(0)
Date: 00:53 on 13 May 2005
The docs on construct are a little thin as to what it really does or
expects. I know it just transforms data into objects without calling
the db, but what does it expect underneath? Does the
data-turned-object have to already exist in the database, or will it
do the right thing if update is called and create a corrisponding new
record?

What I need to do is to pass some data to construct() to get the
desired objects, but I don't want any record to exist in the database
until I do more futxing and then call update().

Is that feasable?

I know I could just wrap the whole process in a transaction and
rollback, but I'm trying to avoid relying on transactions being
available.

-=3DChris

construct + autoupdate(0)
Christopher Laco 00:53 on 13 May 2005

Re: construct + autoupdate(0)
Perrin Harkins 03:22 on 13 May 2005

Re: construct + autoupdate(0)
Tony Bowden 07:31 on 13 May 2005

Re: construct + autoupdate(0)
Bill Moseley 00:39 on 22 Jun 2005

Re: construct + autoupdate(0)
Joss Shaw 08:33 on 13 May 2005

Generated at 16:36 on 28 Jul 2005 by mariachi v0.52