Hi, just a little question about mysql insert into location. I might be wrong here, but please be patient whith me. Im not too good to read through the source tree.... :-)
Would there be anything wrong with changing the insert statement from insert into..... to: insert into.....on duplicate key update.....
(my sipp register stress-test scenario gave me this idea....)
br hw
Hi Helge,
duplicated entries in location table should never happen. Can you describe the scenario you get this?
also your suggestion cannot be put in practice due limitation of the internal DB api - it is not so complex to allow such mysql commands. Also I'm not sure if this syntax in SQL 99 compliant and is not something mysql specific.
regards, bogdan
Helge Waastad wrote:
Hi, just a little question about mysql insert into location. I might be wrong here, but please be patient whith me. Im not too good to read through the source tree.... :-)
Would there be anything wrong with changing the insert statement from insert into..... to: insert into.....on duplicate key update.....
(my sipp register stress-test scenario gave me this idea....)
br hw
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hi, No you are correct. This is not SQL92 but MySQL specific.
I am stress-testing my registrar using sipp, and every register has the same primary keys, which then generates a duplicate key error from the database.
br hw
fre, 01,.12.2006 kl. 13.19 +0200, skrev Bogdan-Andrei Iancu:
Hi Helge,
duplicated entries in location table should never happen. Can you describe the scenario you get this?
also your suggestion cannot be put in practice due limitation of the internal DB api - it is not so complex to allow such mysql commands. Also I'm not sure if this syntax in SQL 99 compliant and is not something mysql specific.
regards, bogdan
Helge Waastad wrote:
Hi, just a little question about mysql insert into location. I might be wrong here, but please be patient whith me. Im not too good to read through the source tree.... :-)
Would there be anything wrong with changing the insert statement from insert into..... to: insert into.....on duplicate key update.....
(my sipp register stress-test scenario gave me this idea....)
br hw
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
I see - but I guess you can configure sipp (not sure how :-/) to generate different AOR-s for register.
regards, bogdan
Helge Waastad wrote:
Hi, No you are correct. This is not SQL92 but MySQL specific.
I am stress-testing my registrar using sipp, and every register has the same primary keys, which then generates a duplicate key error from the database.
br hw
fre, 01,.12.2006 kl. 13.19 +0200, skrev Bogdan-Andrei Iancu:
Hi Helge,
duplicated entries in location table should never happen. Can you describe the scenario you get this?
also your suggestion cannot be put in practice due limitation of the internal DB api - it is not so complex to allow such mysql commands. Also I'm not sure if this syntax in SQL 99 compliant and is not something mysql specific.
regards, bogdan
Helge Waastad wrote:
Hi, just a little question about mysql insert into location. I might be wrong here, but please be patient whith me. Im not too good to read through the source tree.... :-)
Would there be anything wrong with changing the insert statement from insert into..... to: insert into.....on duplicate key update.....
(my sipp register stress-test scenario gave me this idea....)
br hw
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
-
Bogdan-Andrei Iancu -
Helge Waastad -
Helge Waastad