On Tue, Jan 12, 2010 at 11:17 PM, thebitguru wrote:
> Oh, I thought someone else might also have to agree, but anyways, I
> see (http://code.djangoproject.com/wiki/Version1.2Roadmap) that the
> complete feature freeze is January 26 so I will check again on
> February 11 :)
>
> I
Oh, I thought someone else might also have to agree, but anyways, I
see (http://code.djangoproject.com/wiki/Version1.2Roadmap) that the
complete feature freeze is January 26 so I will check again on
February 11 :)
I changed the version to 1.2alpha.
Thanks,
Farhan
On Jan 12, 4:50 am, Russell
On Tue, Jan 12, 2010 at 12:05 PM, thebitguru wrote:
> Can we please get a final decision on this please?
I was under the impression I *had* given a final decision - we should
reject Inf and NaN as invalid values.
The ticket hasn't been closed because we're not focussing on bug
Can we please get a final decision on this please?
- Farhan
On Dec 9 2009, 8:17 pm, Farhan Ahmad wrote:
> The existing patch and tests are coded to behave like this so those should
> be good. I added our discussion to the ticket for historical purposes. I
> don't have to do
The existing patch and tests are coded to behave like this so those should
be good. I added our discussion to the ticket for historical purposes. I
don't have to do anything more from here on so I will wait for the final
decision.
Thanks,
Farhan
On Wed, Dec 9, 2009 at 4:41 AM, Russell
On Tue, Dec 8, 2009 at 10:18 AM, thebitguru wrote:
> OK, here is what I have gathered about the databases listed under
> DATABASE_ENGINE [4].
>
> Postgresql 8: Supports all three, +/-Inf and NaN [0]
> MySQL: No support for either NaN or Inf [1]
> sqlite3: No support for either
OK, here is what I have gathered about the databases listed under
DATABASE_ENGINE [4].
Postgresql 8: Supports all three, +/-Inf and NaN [0]
MySQL: No support for either NaN or Inf [1]
sqlite3: No support for either NaN or Inf [2]
Oracle: Supports all three [3]
So, we have a 50/50 split. What do
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
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
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
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
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/
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/
>>
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
14 matches
Mail list logo