firebird-net-provider

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

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

That sounds great - how about a collection of field names in the
FbCommandBuilder specifying the fields to check?? That way we could
choose to use a generator instead of a timestamp.

builder.FieldsToCheck =3D "myprimarykey,mytimestamp";

John

-----Original Message-----
> Opinions ???
   The fourth variant -- WHERE is generated on primary key fields and
field with fixed-name (for example "TIMESTAMP" or "LAST_MODIFIED").
  =20


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli=
ck
_______________________________________________
Firebird-net-provider mailing list
Fir...@li...
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider

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

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

[Dmitry A. <fd...@do...>]

"JS.staff" wrote:

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

   I thinking about this too, but current we have mode with automatic
primary key selecting... :-)
   In best case, my opinion: 
     if FieldsToCheck empty -- use Behaivor (AllFields or no...)
     or 
     to FbCommandBehaivor add new mode -- ListFields or similar... :)

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

[<car...@te...>]

Hello:

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

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




--
Best regards

Carlos Guzmán Álvarez
Vigo-Spain

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

[Dmitry A. <fd...@ua...>]

Hello Carlos,

Friday, March 12, 2004, 3:41:52 PM, you wrote:

>> builder.FieldsToCheck = "myprimarykey,mytimestamp";
CGÁ> Huummm i don't see this as needed ...
   Some peoples doing lock with pk+timestamp+username_what_set_lock :)
   I consider that this it is enough exclusive event, and real need in
   him presently no. Yes, this was not bad -- universal generation of
   the field where even for undefined behaivor ;). But I consider that
   presently this possible not to do. :)

-- 
Best regards,
 Dmitry                            mailto:fd...@ua...

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

[<car...@te...>]

Hello:

>    Some peoples doing lock with pk+timestamp+username_what_set_lock :)

And another people will do this in another way ;) but i want to mantain 
the compatibility with other .NET providers ;)


For now i will do the implementation as i described in the other email.



--
Best regards

Carlos Guzmán Álvarez
Vigo-Spain

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

[Dmitry A. <fd...@ua...>]

Hello Carlos,

Friday, March 12, 2004, 4:48:56 PM, you wrote:

>>    Some peoples doing lock with
>> pk+timestamp+username_what_set_lock :)
CGÁ> And another people will do this in another way ;) but i want to mantain
CGÁ> the compatibility with other .NET providers ;)
   compatibility from this and does not damage if contribute new
   importance in CommandBehaivour, for activation use this field :-)

CGÁ> For now i will do the implementation as i described in the other email.
   It's fine! :)

-- 
Best regards,
 Dmitry                            mailto:fd...@ua...