Re: Switch to database-level autocommit

2013-03-04 Thread Shai Berger
Hi Florian and everybody, On Sunday 03 March 2013, Florian Apolloner wrote: > On Sunday, March 3, 2013 12:27:47 AM UTC+1, Shai Berger wrote: > > > I also believe that it beats the alternative — namely, live with the > > > > > > current behavior forever. > > > > I sincerely hope [...] that

Re: Switch to database-level autocommit

2013-03-04 Thread Shai Berger
Hi, On Monday 04 March 2013, Aymeric Augustin wrote: > On 4 mars 2013, at 04:04, Shai Berger wrote: > > you need to be sure that, in all these places, either reads don't > > really affect consequent writes, or some constraint holds that is > > equivalent to serializability --

Splicing Geometry by bounding box

2013-03-04 Thread John Baker
Hey I am currently working on a geolocation based game that utilizes a geodjango application to manage querying, parsing, and server geographical data to our client. We are currently using PostGIS to store our OSM data. We are using the OSM tilename system throughout our project and some of our

Re: Switch to database-level autocommit

2013-03-04 Thread Christophe Pettus
On Mar 4, 2013, at 7:24 AM, Aymeric Augustin wrote: > PostgreSQL and Oracle use the "read committed" ... Sorry, replied too soon! > The reasoning and the conclusion still stand. Agreed. -- -- Christophe Pettus x...@thebuild.com -- You received this message because you are subscribed to

Re: Switch to database-level autocommit

2013-03-04 Thread Christophe Pettus
On Mar 4, 2013, at 5:00 AM, Aymeric Augustin wrote: > PostgreSQL and Oracle use the "repeatable read" isolation level by default. Without explicitly changing it, PostgreSQL's default is READ COMMITTED. Or are we setting it explicitly to REPEATABLE READ in the new model? -- -- Christophe

Re: Switch to database-level autocommit

2013-03-04 Thread Aymeric Augustin
On 4 mars 2013, at 16:04, Andrey Antukh wrote: > If not I'am wrong, postgresql uses "read commited" by default and mysql > "repeatable read" Sorry, I swapped the isolation level names when I wrote the explanation. The correct version is: PostgreSQL and Oracle use the "read

Re: first() and last(), earliest() and latest()

2013-03-04 Thread Selwin Ong
+1 for the first syntax too :) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send

Re: Switch to database-level autocommit

2013-03-04 Thread Florian Apolloner
Hi, On Monday, March 4, 2013 2:00:03 PM UTC+1, Aymeric Augustin wrote: > > PostgreSQL and Oracle use the "repeatable read" isolation level by > default. According to http://www.postgresql.org/docs/9.1/static/transaction-iso.html PG uses "read commited" as default. > MySQL uses "read

Re: Switch to database-level autocommit

2013-03-04 Thread Andrey Antukh
If not I'am wrong, postgresql uses "read commited" by default and mysql "repeatable read" http://www.postgresql.org/docs/9.1/static/transaction-iso.html -> "Read Committed is the default isolation level in PostgreSQL. " http://dev.mysql.com/doc/refman/5.0/en/innodb-transaction-model.html -> "In

Re: Switch to database-level autocommit

2013-03-04 Thread Aymeric Augustin
On 4 mars 2013, at 04:04, Shai Berger wrote: > you need to be sure that, in all these places, either reads don't > really affect consequent writes, or some constraint holds that is equivalent > to > serializability -- otherwise, negative effect is possible. PostgreSQL and

Re: Switch to database-level autocommit

2013-03-04 Thread Aymeric Augustin
On 4 mars 2013, at 01:07, Shai Berger wrote: >> On 1 mars 2013, at 13:48, Aymeric Augustin >> wrote: >> >> I'd like to add an @atomic decorator that: >> - Really guarantees atomicity, by raising an exception if you attempt >> commit