On Wed, Apr 27, 2011 at 2:30 PM, Tobias McNulty <[email protected]>wrote:
> On Wed, Apr 27, 2011 at 9:31 AM, Luke Plant <[email protected]> wrote: > >> <snip> ... If you need to store >> infinity in a database column, it's better to know sooner that your >> database doesn't support it so you can find one that does. >> > > +1 > -- > Tobias McNulty, Managing Partner > Caktus Consulting Group, LLC > http://www.caktusgroup.com > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > Storing sys.maxint in place of float('inf') in a database column is so wildly inappropriate that it actually takes someone more articulate than me to describe, and as such any emulation will fail on similar grounds (notably that it dupes a valid value), however I don't think that should prevent us from supporting it on DBs that do support it (PostgreSQL doing the right thing... again!) Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
