That error has been around forever. The best I can tell
it doesn't hurt anything.
-tim
> -----Original Message-----
> From: Guilherme Ceschiatti [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, September 19, 2000 6:02 PM
> To: Orion-Interest
> Subject: RE: ATM example with PostgreSQL
>
>
> On Fri, 15 Sep 2000, Arved Sandstrom wrote:
> > Hi, Guiga
>
> Hi!
>
> Thanks for your attention. I used to had the "null problem"
> too, but I fix it
> changing null="null" to null="", as you said. Now, remains a
> error message
> saying:
>
> ERROR: parser error at or near ")" .
>
> Any hint to fix it?
>
> > What's the nature of the errors? I found that PostgreSQL
> 6.5.3, when I tried
> > that with Orion and CMP, didn't like explicit NULL at all,
> so I edited
> > "config/database-schemas/postgresql.xml" to change null=""
> rather than
> > null="null". Then it worked fine. This strikes me as a bug
> in PostgreSQL
> > 6.5.x, since the docs indicate that an explicit declaration
> of NULL on a
> > column is OK. Don't know about PostgreSQL 7.0.
>
> []s
> Guilherme Ceschiatti
> [EMAIL PROTECTED]
>
