RE: [Firebird-net-provider] FbCommandBuilder - where's clause rule[Scanned]

[JS.staff <jsp...@ec...>]

Well, just thought instead of fixing people to using pk, or =
pk+timestamp, or all, you could allow them to choose which fields to =
check - for whatever reason they choose.

Maybe someone would want to use a integer 'generation' value instead of =
a timestamp to control concurrency, for example. So the trigger would =
have something like

Before update trigger:
	genfield =3D gen_id(gennumber,1);

And they you'd do:

Update mytable set xxxx where pk =3D @mypk and genfield =3D @genfield

John


-----Original Message-----
From: Carlos Guzm=E1n =C1lvarez [mailto:car...@te...]=20
Sent: 12 March 2004 13:42
To: JS.staff
Cc: firebird-net-provider
Subject: Re: [Firebird-net-provider] FbCommandBuilder - where's clause =
rule[Scanned]


Hello:

> That sounds great - how about a collection of field names in the=20
> FbCommandBuilder specifying the fields to check?? That way we could=20
> choose to use a generator instead of a timestamp.
>=20
> builder.FieldsToCheck =3D "myprimarykey,mytimestamp";

Huummm i don't see this as needed ...




--
Best regards

Carlos Guzm=E1n =C1lvarez
Vigo-Spain