ah, ok. danke.
Jacob Kaplan-Moss wrote:
> On 10/23/07, Derek Anderson <[EMAIL PROTECTED]> wrote:
>> are column defaults not supposed to be set by django under postgres?
>
> Django doesn't set defaults in the database at all.
>
> The basic reason is that too many defaults simply couldn't be
> represented in a database -- especially those oriented around
> callables. It's not worth doing if it only works some of the time.
>
> IIRC there was a pretty big argument about this some time back; you
> may want to search the archives for that.
>
> Jacob
>
> >
>
--
looking to buy or sell anything?
try: http://allurstuff.com
it's a classified ads service that
shows on a map where the seller is
(think craigslist + google maps)
plus it's 100% free :)
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
