Thanks Hannes!!! Sorry, I'm confused because I am _not_ using the LOCKED command in my COPY INTO command (double-check my commands). Do I need to add something to specify I do _not_ want it locked? NOT LOCKED (doesn't work)..

Are you sure the behavior I've described is appropriate? :(

On Fri, Feb 22, 2013 at 1:47 PM, Hannes Mühleisen <Hannes.Muehleisen@cwi.nl> wrote:

Hi Anthony,

On 22/02/13 19:44, Anthony Damico wrote:

Hi, I am using a brand new mserver.exe instance of MonetDB5 on Windows.
I am getting the error: "COMMIT: transaction is aborted because of
concurency conflicts, will ROLLBACK instead" that I'm not sure I
should? Shouldn't I be able to use the COPY command on two separate CSV
files into two separate data tables at once? I don't think this
behavior is correct, but maybe I'm wrong? :/

You can do that, but not with the LOCKED keyword. That says basically, that the COPY INTO is the only thing happening on the DB at that time and that it can forget about all the transactional stuff. Once you are doing two such things, it gets messy. So, either only run one COPY statement or remove LOCKED.

Best,

Hannes (who is still at work writing a paper... you are mentioned in the Acknowledgements!)

_______________________________________________
users-list mailing list
users-list@monetdb.org
http://mail.monetdb.org/mailman/listinfo/users-list