On Thu 12 Jul 2007, Gary Wilson wrote:
> Ben Ford wrote:
> > Peter,
> > I ran into this problem when I was bringing the multi-db branch up to
> > date and was so busy I forgot to tell anyone! (My bad) I fixed it, but
> > it was on another machine. It's a pretty simple change, but the exact
> > dif
Yes, word for word damnit!
Wish I'd seen that before I started messing... Still it taught me a bit more
about postgres I guess so it's all good! :-)
Cheers,
Ben
On 12/07/07, Gary Wilson <[EMAIL PROTECTED]> wrote:
>
>
> Ben Ford wrote:
> > Peter,
> > I ran into this problem when I was bringing the
Ben Ford wrote:
> Peter,
> I ran into this problem when I was bringing the multi-db branch up to date
> and was so busy I forgot to tell anyone! (My bad) I fixed it, but it was on
> another machine. It's a pretty simple change, but the exact diff escapes me
> at the moment! Is there a ticket on th
Peter,
I ran into this problem when I was bringing the multi-db branch up to date
and was so busy I forgot to tell anyone! (My bad) I fixed it, but it was on
another machine. It's a pretty simple change, but the exact diff escapes me
at the moment! Is there a ticket on this, as I think it might be
When running "python manage.py inspectdb" against the following postgresql
table:
# \d auth_message
Table "public.auth_message"
Column | Type | Modifiers
-+-+---
id
