Re: About GSoC 2013

2013-03-06 Thread Russell Keith-Magee
On Wed, Mar 6, 2013 at 8:04 PM, Mayur Patil wrote: > Hello, > >Most of the organizations(Eclipse,Fedora, > >VLC etc) have created their GSoC Idea page. > >Where is Idea page for Django? > >I am eagerly waiting for it !! > Hi Mayur, The period for organizations to apply for GSoC 2

Re: Switch to database-level autocommit

2013-03-06 Thread Jacob Kaplan-Moss
To clarify a little bit, the reasons I think it's a good idea are because: * It's simple and clean. * It doesn't require another setting, nor new middleware methods, nor new anything actually. * It makes Django inter-op a tiny bit better (if you want to use Django's ORM and request-linked commits

Re: Switch to database-level autocommit

2013-03-06 Thread Aymeric Augustin
On 5 mars 2013, at 23:13, Aymeric Augustin wrote: > For lack of a better idea, I'm considering deprecating the middleware and > replacing it with a setting. This doesn't qualify as loose coupling; better > ideas welcome! Jacob just suggested on IRC using a WSGI middleware. It's two lines of

Re: Ticket #15363 -- Normalization of the queryset methods name

2013-03-06 Thread charettes
Unfortunately this would break in subtle in confusing ways in inheritance scenarios. Say you've defined the following Manager subclass prior to Django 1.6 and we're only raising a warning on Manager.get_query_set calls.: class ActiveManager(models.Manager): def get_query_set(self, *args,

Re: Ticket #15363 -- Normalization of the queryset methods name

2013-03-06 Thread Jacob Kaplan-Moss
On Wed, Mar 6, 2013 at 12:21 PM, charettes wrote: > The use of the metaclass make sure you're not shooting yourself in the foot > all and all the metaclass subclassing trouble should only concern a minority > of users who most probably know what they're doing. Ah, OK, that's the missing part I wa

Re: Moving database backends out of the core

2013-03-06 Thread Michael Manfre
On Wed, Mar 6, 2013 at 12:47 PM, Florian Apolloner wrote: > On Wednesday, March 6, 2013 3:32:45 PM UTC+1, Michael Manfre wrote: >> >> The lack of data validation is definitely a nogo for production sites, >> but imo sqlite in production is also a nogo. >> > > Right, but shipping Django with a non

Re: Moving database backends out of the core

2013-03-06 Thread Florian Apolloner
Hi, On Wednesday, March 6, 2013 3:32:45 PM UTC+1, Michael Manfre wrote: > > The lack of data validation is definitely a nogo for production sites, but > imo sqlite in production is also a nogo. > Right, but shipping Django with a non production db might send interesting signals to endusers ;)

Re: Ticket #15363 -- Normalization of the queryset methods name

2013-03-06 Thread Aymeric Augustin
There's a good, although non-obvious, reason. Without the metaclass, a method overridden in the subclass with the old name would be silently skipped. -- Aymeric. Le 6 mars 2013 à 16:30, Jacob Kaplan-Moss a écrit : > Hm. > > I'm +1 on cleaning up the names but do we *really* have to use

Re: Ticket #15363 -- Normalization of the queryset methods name

2013-03-06 Thread Jacob Kaplan-Moss
Hm. I'm +1 on cleaning up the names but do we *really* have to use a metaclass for this? Seems to me this is "gratuitous use of a metaclass" territory, especially given the shenanigans you have to go through with subclassing the metaclass. I'd be a lot happier with this patch if it just did t

Re: Switch to database-level autocommit

2013-03-06 Thread Javier Guerra Giraldez
On Wed, Mar 6, 2013 at 4:15 AM, Jeremy Dunck wrote: > I, for one, would prefer that we not recommend TransactionMiddleware > so highly. then what would be the recommended option to have transactions tied to the request/response cycle? probably @commit_on_success for every view that modifies the

Re: Moving database backends out of the core

2013-03-06 Thread Michael Manfre
Hi Andre, On Tuesday, March 5, 2013 5:39:29 PM UTC-5, Andre Terra wrote: > > If I may weigh in on the matter as an outsider, if we consider "The Django > Project" as a "business", insofar as it aims to have as many users and be > as ubiquitous as possible, there's considerable value in having MS

Re: Moving database backends out of the core

2013-03-06 Thread Michael Manfre
On Tuesday, March 5, 2013 5:01:01 PM UTC-5, Florian Apolloner wrote: > > Hi Shai, > > On Tuesday, March 5, 2013 10:32:29 PM UTC+1, Shai Berger wrote: >> >> In recent years, I have been the main contributor to South's MSSQL and >> Oracle >> backends. I am biased towards having MSSQL treated as a

Re: Moving database backends out of the core

2013-03-06 Thread Michael Manfre
On Tuesday, March 5, 2013 3:31:59 PM UTC-5, Florian Apolloner wrote: > > Hi, > > While I agree that moving database adapters out of core has some merit, I > don't think that having sqlite as a reference implementation is a good > idea: For one some features are somewhat hacky in sqlite (and peo

Re: Switch to database-level autocommit

2013-03-06 Thread kayess
On Wednesday, 6 March 2013 16:12:18 UTC+7, jdunck wrote: > > Can > you give a concrete example of an exception being raised at commit > time? > Postgres allows for things like foreign key integrity checks to be made on commit (rather than when the data is entered). This makes it significantl

Re: Switch to database-level autocommit

2013-03-06 Thread Aymeric Augustin
On 6 mars 2013, at 08:49, Ian Kelly wrote: > On Tue, Mar 5, 2013 at 3:13 PM, Aymeric Augustin > wrote: >> In the mean time, I discovered that it's impossible to implement >> TransactionMiddleware reliably as a middleware, because there's no guarantee >> that process_response or process_exception

About GSoC 2013

2013-03-06 Thread Mayur Patil
Hello, Most of the organizations(Eclipse,Fedora, VLC etc) have created their GSoC Idea page. Where is Idea page for Django? I am eagerly waiting for it !! Seeking for Guidance, Thank you !! -- *Cheers, Mayur*. -- You received this message because you are subscribed to th

Re: Switch to database-level autocommit

2013-03-06 Thread Jeremy Dunck
I, for one, would prefer that we not recommend TransactionMiddleware so highly. Now that I'm doing active development with Rails, it's quite clear to me that a major difference in the ORM layers are which DB they grew up with -- the django orm is tuned best to postgres, while working passably on m

Re: Switch to database-level autocommit

2013-03-06 Thread Jeremy Dunck
I'm not sure what you're referring to here - integrity, uniqueness, and locking are handled at the individual query level - transactions just cause locks to be held (if needed) until commit or rollback. Can you give a concrete example of an exception being raised at commit time? On Tue, Mar 5, 2

Re: Switch to database-level autocommit

2013-03-06 Thread Jeremy Dunck
On Mon, Mar 4, 2013 at 1:34 AM, Aymeric Augustin wrote: > On 4 mars 2013, at 01:07, Shai Berger wrote: ... >> The use of savepoints in Django apps so far has been very little, as far as >> I know. One point >> I'm unsure of is the interaction of savepoints with cursors, since querysets >> are l

Re: Moving database backends out of the core

2013-03-06 Thread Florian Apolloner
Hi Andre, On Tuesday, March 5, 2013 11:39:29 PM UTC+1, Andre Terra wrote: > > but at work I'm restricted to corporate rules, MS SQL or Oracle, and > Windows. Right, that's probably one of the reasons why Oracle is in core (aside from the fact that we were completely monolithic at that time).

Re: Switch to database-level autocommit

2013-03-06 Thread Florian Apolloner
On Wednesday, March 6, 2013 8:49:37 AM UTC+1, Ian wrote: > > On Tue, Mar 5, 2013 at 3:13 PM, Aymeric Augustin > > wrote: > > In the mean time, I discovered that it's impossible to implement > > TransactionMiddleware reliably as a middleware, because there's no > guarantee > > that process_resp