Hi!
On Nov 30, 2008, at 12:55 PM, Roland Bouman wrote:
On Sun, Nov 30, 2008 at 8:56 PM, Brian Aker <[EMAIL PROTECTED]> wrote:
Is there any advantage in CSV having delete or update? Truncate I
understand....
Would be nice to have, but indeed - not essential.
The reason I ask is that our architecture is quickly moving to the
point where engines have to be either upgraded to be row level
locking, or they need to be tossed.
CSV is row level locking for UPDATE and DELETE. For INSERT though it
is row.
This problem, namely easy data load, needs a complete rethinking.
A set of questions to ask:
1) Does data loading need to be JOINABLE?
2) Do you want to leave it in its original container and be able to
use it?
3) Do you want to be able to update it from within the database?
If we provided a good tool, should this even be in the database, or a
part of a new protocol?
Cheers,
-Brian
--
_______________________________________________________
Brian "Krow" Aker, brian at tangent.org
Seattle, Washington
http://krow.net/ <-- Me
http://tangent.org/ <-- Software
_______________________________________________________
You can't grep a dead tree.
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp