Re: Problem with history view in admin page

2009-11-24 Thread Richard Laager
On Tue, 2009-11-24 at 20:54 -0800, Mario Briggs wrote: > Instead we will let users run into errors when they do a '=' compare > of a Django Text type, and then let them ponder whether they need that > column as a CLOB in the backend. Shouldn't something be changing that = into a LIKE (and escaping

Re: Problem with history view in admin page

2009-11-24 Thread Mario Briggs
Russell, > >> Well, Django doesn't make the decision to use CLOB - that's in the > >> hands of your backend. In the same circumstances, SQLite and Postgres > >> use 'text'. MySQL uses 'longtext'. Oracle uses 'NCLOB' I understand that the decision to what 'Text' should be mapped to is the choice o

Re: How hard would it be to make bits of Django compatible with async servers?

2009-11-24 Thread Russell Keith-Magee
On Mon, Nov 23, 2009 at 11:38 PM, Simon Willison wrote: > I've been getting very excited about Node.js recently: > > http://simonwillison.net/2009/Nov/23/node/ > > It's basically Twisted / Tornado but in JavaScript, and with the huge > advantage that, because it's brand new, it doesn't have any le

Re: Problem with history view in admin page

2009-11-24 Thread Karen Tracey
On Tue, Nov 24, 2009 at 7:09 PM, Russell Keith-Magee wrote: > This is a slightly moot point, though; Django defines the admin log > object_id using a TextField, and changing this would be a big > backwards incompatibility. > > Also I believe there's at least one other place in Django that does si

Re: Problem with history view in admin page

2009-11-24 Thread Russell Keith-Magee
On Wed, Nov 25, 2009 at 1:25 AM, Ian Kelly wrote: > On Mon, Nov 23, 2009 at 11:00 PM, Russell Keith-Magee > wrote: >> On Tue, Nov 24, 2009 at 1:07 PM, Mario Briggs >> wrote: >>> I agree that INTEGER is not the right choice, but then so too is CLOB. >>> How long is this string-serialized represe

Re: Why not datetime.utcnow() in auto_now/auto_now_add

2009-11-24 Thread Russell Keith-Magee
On Wed, Nov 25, 2009 at 12:10 AM, jedie wrote: > DateTimeField "auto_now" and "auto_now_add" used datetime.now(). But > why this? IMHO it's better to use datetime.utcnow(), isn't it? Why would it be? A datetime field isn't necessarily stored in UTC. It uses datetime.now() because that will return

Re: Oracle/GIS Testers Needed

2009-11-24 Thread redetin
On Sat, Nov 21, 2009 at 1:36 AM, Alex Gaynor wrote: > On Fri, Nov 20, 2009 at 3:56 PM, Karen Tracey wrote: > >> Just running the Oracle tests is enough for now. I've fixed the error > >> you spotted with the stray import left over and pushed that to github. > > > > I get 6 failures and 26 error

Re: Problem with history view in admin page

2009-11-24 Thread Ian Kelly
On Mon, Nov 23, 2009 at 11:00 PM, Russell Keith-Magee wrote: > On Tue, Nov 24, 2009 at 1:07 PM, Mario Briggs wrote: >> I agree that INTEGER is not the right choice, but then so too is CLOB. >> How long is this string-serialized representation going to be? greater >> than 4000 characters ? Varchar

Why not datetime.utcnow() in auto_now/auto_now_add

2009-11-24 Thread jedie
DateTimeField "auto_now" and "auto_now_add" used datetime.now(). But why this? IMHO it's better to use datetime.utcnow(), isn't it? Mfg. Jens Diemer -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to djan

django-firebird projects news

2009-11-24 Thread mariuz
Hello everyone, I want to make a summary of the changes implemented in recent times about the project django-firebird: http://code.google.com/p/django-firebird/ http://tech.groups.yahoo.com/group/firebird-python/message/254 -- You received this message because you are subscribed to the Google G