search

QuillLittlefeather / openmetaverse

Automatically exported from code.google.com/p/openmetaverse
0 stars 0 forks source link

Replace REPLACE INTO queries with ON DUPLICATE KEY queries #1

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Several of our Add* queries use "REPLACE INTO" where "ON DUPLICATE KEY" is
a better match for the semantics we need and would yield a performance
improvement.

Original issue reported on code.google.com by jhurlima...@gmail.com on 5 Feb 2010 at 12:34

GoogleCodeExporter commented 9 years ago 
John, are these in some of the new methods added e.g. in the public repo vs the 
ones
still in the private repo? I did a simple grep and didn't find anywhere I used
REPLACE INTO

Original comment by jimradford@gmail.com on 5 Feb 2010 at 10:20

GoogleCodeExporter commented 9 years ago 
This was from some of the methods I added. I think I have it down to one 
REPLACE INTO
call that will be easy to replace, so I can close this out soon.

Original comment by jhurlima...@gmail.com on 10 Feb 2010 at 8:00

GoogleCodeExporter commented 9 years ago 
AddScene, AddUser, and AddUserData are the three files that contain REPLACE 
INTO queries.

Original comment by jhurlima...@gmail.com on 4 Mar 2010 at 5:23

GoogleCodeExporter commented 9 years ago 
Based on current discussions, if we're going to spend work improving backend 
support it would be to switch to MongoDB exclusively. Marking as WontFix

Original comment by jhurlima...@gmail.com on 11 Aug 2010 at 11:26