If you are worried about concurrency. you could add a TIMESTAMP field to
your tables. It works like this. When you read the record you also read
the TIMESTAMP value of the last time the record was updated. When you
attempt to commit your changes into the database, compare that datetime to
the one currently in the record. If it doesn't match, you know that
someone (or something) already changed the record since you started
There are several ways to detect the change:
an UPDATE of 0 records
or - a transaction wrapped around a read check of the current date
followed by an update statement (InnoDB)
or - a LOCK/UNLOCK wrapper around a read check of the date with
How you handle edit conflicts is rather application specific. Your options
can be summarized as:
1) Forget the changes you are attempting to make and start over with the
2) Merge your changes with those already made (requires field by field
3) Overwrite the existing changes with your changes.
I concur with James, I don't databind any elements. I found that database
automation only works reliably for the most trivial of cases and I firmly
believe that I have saved time by constructing my own SQL statements. Not
only do I *know* that it will be an optimal statement, I won't have to
worry too much about a component upgrade automagically writing platform
specific statements because it's trying to optimize for MS Access or MS
SQL Server and not MySQL.
My recommendation too, use the connections and recordsets for reading data
and manage your own inserts and updates through direct SQL statements.
Unimin Corporation - Spruce Pine
streamlake@stripped wrote on 12/22/2004 03:33:22 AM:
> Thanks James,
> I'm beginning to think that your suggestion looks to be a correct
> CommandBuilder lets me save some coding but it doesn't look particularly
> flexible, or maybe I don't know it well enough... :-)
> The same happens with automatic data binding with TextBoxes
> (Binding, BindingContext,
> Parse and Format events, etc), it doesn't look much flexible apart from
> basic operations, or at least it doesn't make me reduce code size.
> Any other suggestions for the float problem?
> >-- Messaggio Originale --
> >From: "James Moore" <banshee@stripped>
> >To: "'Frank'" <streamlake@stripped>, <dotnet@stripped>
> >Subject: RE: About float fields
> >Date: Tue, 21 Dec 2004 17:32:51 -0800
> >My personal solution is to not use automatically generated SQL (ie,
> >CommandBuilder.) I find that for the simple case building the commands
> >myself is simple anyway, and in the more complex case CommandBuilder
> >do what I need. Not really a solution to your problem, but it's
> >to think about.
> > - James
> Tiscali Adsl 2 Mega Free: l'adsl piu' veloce e' gratis!
> Naviga libero dai costi fissi con Tiscali Adsl 2 Mega Free, l'adsl Free
> piu' veloce in Italia. In piu', se ti abboni entro il 7 gennaio 2005,
> navighi gratis fino al 31 marzo. E il costo di adesione e' GRATIS.
> MySQL on .NET Mailing List
> For list archives: http://lists.mysql.com/dotnet
> To unsubscribe: http://lists.mysql.com/dotnet?unsub=1