Re: Non-trivial question: New subclass companion for Stacked/Tabular Inlines

2009-11-08 Thread Tim
I'm aware that the admin-ui branch is to be folded into the 1.2 release of Django-- I'm not very familiar with the branch, and docmentation is hard to find on it (in my opinion), short of running the branch myself. Will it replace the need for the current InlineModelAdmin subclasses entirely? I

Re: autocommit, INSERT... RETURNING and PostgreSQL 8.2+

2009-11-08 Thread Christophe Pettus
On Nov 8, 2009, at 8:39 AM, Seb Potter wrote: > transaction pooling Ah, of course. Thank you! -- -- Christophe Pettus x...@thebuild.com --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" grou

Re: Non-trivial question: New subclass companion for Stacked/Tabular Inlines

2009-11-08 Thread andybak
I'm pretty sure Zain has made all the inline types sortable on his admin-ui branch. On Nov 8, 7:58 am, Tim wrote: > I very much like the look of that one, but I'm not sure if it > completely fills the need I want for my own project.  All of the > fields need to be quickly visible, without needin

Re: autocommit, INSERT... RETURNING and PostgreSQL 8.2+

2009-11-08 Thread Seb Potter
Hi Christophe, When you're running postgres with autocommit and transaction pooling (ie: the lifetime of a connection is a single transaction - essential for high-performance sites), you run the risk of returning an incorrect id by calling: cursor.execute("SELECT CURRVAL('\"%s_%s_seq\"')" % (tabl

Re: #10509 (Better handling of database-specific information)

2009-11-08 Thread Russell Keith-Magee
On Sat, Nov 7, 2009 at 12:50 PM, Christophe Pettus wrote: > > Greetings, > > As part of proposing a patch for a bug I filed (#12180), I ran across > this ticket, and took the liberty of claiming it.  Since I'm > relatively new to working on Django code proper, I wanted to start a > discussion abo