"Dominic J. Eidson" schrieb: > > ... > > What if I do a SELECT to check for a row. Then I do a INSERT. But between > > SELECT and INSERT someone else inserted a row. NO I do not think that "good > > programming" will solve this. > > Good design, together with good implementation, gets you a long way. > Ok, now the question may be asked: How can this pattern be solved (to use a very modern word ..). a) Prevent such a situation :-) b) Try to insert a "lock"-mechanism in your code Marten
- Re: SV: [GENERAL] MySQL and PostgreSQL speed compare Alfred Perlstein
- Re: SV: [GENERAL] MySQL and PostgreSQL speed compa... Lamar Owen
- Re: SV: [GENERAL] MySQL and PostgreSQL speed c... Gordan Bobic
- Re: SV: [GENERAL] MySQL and PostgreSQL speed compa... John Burski
- Re: SV: [GENERAL] MySQL and PostgreSQL speed c... Ron Chmara
- Re: SV: [GENERAL] MySQL and PostgreSQL spe... Gordan Bobic
- Re: SV: [GENERAL] MySQL and PostgreSQL speed compa... Ron Chmara
- Re: [GENERAL] MySQL and PostgreSQL speed compare Benjamin Pflugmann
- Re: [GENERAL] MySQL and PostgreSQL speed compare Marten Feldtmann
- Re: [GENERAL] MySQL and PostgreSQL speed compare Gordan Bobic