On Wed, Nov 25, 2009 at 4:24 PM, Yuri Baburov wrote:
> Hi Russell,
>
> is it possible to introduce some new field type
> ShortTextField for that purpose, that will be by default
> `varchar(4000)` on Oracle and DB2 who supports long varchars, and
> `text` on other backends like it was before, excep
On Thu, Nov 26, 2009 at 1:42 AM, Jani Tiainen wrote:
> On Thu, 2009-11-26 at 01:28 -0600, Alex Gaynor wrote:
>
>>
>> Thanks for taking the time to run all of those! All of those
>> ConnectionDoesNotExist errors come from the fact that the multidb
>> tests expect you to have more than 1 DB set up
On Thu, 2009-11-26 at 01:28 -0600, Alex Gaynor wrote:
>
> Thanks for taking the time to run all of those! All of those
> ConnectionDoesNotExist errors come from the fact that the multidb
> tests expect you to have more than 1 DB set up in your settings file,
> the rigth solution here is probably
On Thu, Nov 26, 2009 at 1:21 AM, Jani Tiainen wrote:
> On Fri, 2009-11-20 at 01:14 -0500, Alex Gaynor wrote:
>> Hey all,
>>
>> Russ and I have been working on getting the multi-db work ready for
>> merge (final stretch here hopefully!), and I just ported the Oracle
>> backend to the slightly updat
On Fri, 2009-11-20 at 01:14 -0500, Alex Gaynor wrote:
> Hey all,
>
> Russ and I have been working on getting the multi-db work ready for
> merge (final stretch here hopefully!), and I just ported the Oracle
> backend to the slightly updated backend arcitecture so it could use
> some testers. If y
OK, you have me convinced :) My assumption was that the developer
changing these options would take the time to ensure that the database
supports it, but I can see why one might assume that if the API
supports it then the database probably does too. I will do a survey
of the django supported data
On Thu, Nov 26, 2009 at 1:52 PM, thebitguru wrote:
> Thanks for the reply, Russ.
>
> I need to revise the patch, but I need some confirmation. I am not
> sure if it is worth determining what all the different databases
> support. I think optional parameters (allow_{inf,nan}=False) that let
> the
Thanks for the reply, Russ.
I need to revise the patch, but I need some confirmation. I am not
sure if it is worth determining what all the different databases
support. I think optional parameters (allow_{inf,nan}=False) that let
the user specify that django should allow these two cases would be
Sorry, I submitted that patch about a month ago and that was the date
stuck in my head :) I just realized that I made my original post only
two days ago. I apologize.
On Nov 25, 12:29 pm, Alex Gaynor wrote:
> On Wed, Nov 25, 2009 at 12:15 PM, thebitguru wrote:
> > Anyone?
>
> > On Nov 23, 6:38
On Thu, Nov 26, 2009 at 12:04 AM, Johannes Dollinger
wrote:
> QuerySet.delete() currently sets the primary key and all nullable
> foreign keys (to deleted objects) of instances passed to signal
> handlers to None. No cache is updated.
>
> Model.delete() will do the same, but as these instances are
On Wed, Nov 25, 2009 at 7:10 PM, jedie wrote:
> On 25 Nov., 00:36, Russell Keith-Magee wrote:
>> Why would it be? A datetime field isn't necessarily stored in UTC. It
>> uses datetime.now() because that will return the same time as
>> settings.TIME_ZONE.
>
> To improve my understanding: What if t
On Thu, Nov 26, 2009 at 2:15 AM, thebitguru wrote:
> Anyone?
>
> On Nov 23, 6:38 pm, thebitguru wrote:
>> Hi,
>>
>> Can I please get some feedback on this ticket? I am hoping that we
>> can get this in soon.
>>
>> http://code.djangoproject.com/ticket/
Echoing Alex's comment - responding to
Oh, forgot there are also signals that might help.
http://docs.djangoproject.com/en/dev/ref/signals/#module-django.core.signals
:)
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googl
Not sure if this would solve the problem, but have a look at
django.utils.ddecorators.decorator_from_middleware.
"""
Given a middleware class (not an instance), returns a view decorator. This
lets you use middleware functionality on a per-view basis.
"""
This also might be best discussed on djang
Hi Serg,
(replying to the list)
On Thu, Nov 26, 2009 at 4:09 AM, serg wrote:
>
> hmm.. yes. it's almost the same i mean.
> but, all middlewares calls for each request... It's bad (imho).
> also in 99.99% cases it wil be work nice...
> thanks!
>
> This method {'filter_ip':True} is unsafe.
>
> Loo
On Tue, Nov 24, 2009 at 3:36 PM, Russell Keith-Magee
wrote:
>
> Time zone handling is definitely something that Django could handle
> better, but simply switching to UTC for certain functions isn't the
> solution.
>
I like the solution proposed on ticket 10587:
http://code.djangoproject.com/ticke
On Wed, Nov 25, 2009 at 12:15 PM, thebitguru wrote:
> Anyone?
>
> On Nov 23, 6:38 pm, thebitguru wrote:
>> Hi,
>>
>> Can I please get some feedback on this ticket? I am hoping that we
>> can get this in soon.
>>
>> http://code.djangoproject.com/ticket/
>>
>> Thanks,
>> Farhan
>
> --
>
> You
Anyone?
On Nov 23, 6:38 pm, thebitguru wrote:
> Hi,
>
> Can I please get some feedback on this ticket? I am hoping that we
> can get this in soon.
>
> http://code.djangoproject.com/ticket/
>
> Thanks,
> Farhan
--
You received this message because you are subscribed to the Google Groups
"D
QuerySet.delete() currently sets the primary key and all nullable
foreign keys (to deleted objects) of instances passed to signal
handlers to None. No cache is updated.
Model.delete() will do the same, but as these instances are collected
by traversing related object descriptors all reverse
On Wed, Nov 25, 2009 at 11:08 PM, serg wrote:
>
> For example:
you can already do something like this (middleware conditional on
urls) via the view middleware mechanism.
in urls:
...
(r'^members/private/', include('members.private.urls'), {'filter_ip':True}),
...
then the middleware:
class Fil
The request processing can be easy if developers of sites can define
prehandlers and posthandlers for each urls.py (or views.py?).
prehandler: the connection middleware. It calls before request
object was created. Only connection detailes needed for prehandler
processing (no session, no user,
On 25 Nov., 00:36, Russell Keith-Magee wrote:
> Why would it be? A datetime field isn't necessarily stored in UTC. It
> uses datetime.now() because that will return the same time as
> settings.TIME_ZONE.
To improve my understanding: What if the server changed and the time
zone is not the same? IM
Hi Russell,
is it possible to introduce some new field type
ShortTextField for that purpose, that will be by default
`varchar(4000)` on Oracle and DB2 who supports long varchars, and
`text` on other backends like it was before, excepting 'smalltext'
instead of 'longtext' for mysql?
I think this is
23 matches
Mail list logo
