Thread: resin-cmp, apache1.3.20, ultradev4, and postgresql7.0 problems

resin-cmp, apache1.3.20, ultradev4, and postgresql7.0 problems

From
tomasz konefal
Date:
hello,

   i'm having trouble getting ultradev to make a connection with a postgresql
database on my server.  does anyone have any experience with this?  i have a
test .jsp script which can pull data out of a test db, but ultradev doesn't
want to make a connection.

when selecting the database connection for postgresql (some info downloaded
from http://www.animaproductions.com/ultra.html) we get the following error:

"While executing inspectConnection in postgresql_jdbc_conn.htm, a JavaScript
error occurred."


i'm not really sure where to look, any help would be appreciated.
cheers,
   twkonefal


Re: resin-cmp, apache1.3.20, ultradev4, and postgresql7.0 problems

From
tony
Date:
On 23 Aug 2001 13:05:51 -0400, tomasz konefal wrote:

>    i'm having trouble getting ultradev to make a connection with a postgresql
> database on my server.  does anyone have any experience with this?  i have a
> test .jsp script which can pull data out of a test db, but ultradev doesn't
> want to make a connection.
>
> when selecting the database connection for postgresql (some info downloaded
> from http://www.animaproductions.com/ultra.html) we get the following error:
>
> "While executing inspectConnection in postgresql_jdbc_conn.htm, a JavaScript
> error occurred."

Where does resin want the postgresql.jar? I have never run resin so I
won't be of much help. However the error message seems to indicate that
the driver is not found.

The location has changed in Tomcat 3.3. I am overloaded with work at the
present time so I will wait untill Tomcat 3.3 gets out of beta before
modifyimg my production server.

Also this really should be on the JDBC list.

Cheers

Tony Grant


valid NULL DATE value

From
Tony Grant
Date:
Hello,

I am importing via pgaccess a text file from another non-postgres
database and the NULL DATE values are written like 00/00/00.

What I have tried is replacing 00/00/00 by 9/9/1999 and setting the
style to european and I am getting 'can't parse /9/1999' errors.

How do I go about importing DATE?

Cheers

Tony Grant

--
RedHat Linux on Sony Vaio C1XD/S
http://www.animaproductions.com/linux2.html
Macromedia UltraDev with PostgreSQL
http://www.animaproductions.com/ultra.html


Re: valid NULL DATE value

From
"Len Morgan"
Date:
> I am importing via pgaccess a text file from another non-postgres
> database and the NULL DATE values are written like 00/00/00.
>
> What I have tried is replacing 00/00/00 by 9/9/1999 and setting the
> style to european and I am getting 'can't parse /9/1999' errors.

Try replacing 00/00/00 with NULL in the text file.  If the text file is
organized to be read by the COPY command, then use \N instead.

len morgan


Re: valid NULL DATE value

From
"Oliver Elphick"
Date:
Tony Grant wrote:
  >Hello,
  >
  >I am importing via pgaccess a text file from another non-postgres
  >database and the NULL DATE values are written like 00/00/00.
  >
  >What I have tried is replacing 00/00/00 by 9/9/1999 and setting the
  >style to european and I am getting 'can't parse /9/1999' errors.
  >
  >How do I go about importing DATE?

With INSERT, leave the field out of the list or insert NULL.

With COPY, specify NULL as \N.  (You can redefine that - see COPY syntax.)

If you have a flat file with 00/00/00 in it, you can modify it with sed:

  sed -e 's|00/00/00|\\N|g' flatfile > newflatfile


--
Oliver Elphick                                Oliver.Elphick@lfix.co.uk
Isle of Wight                              http://www.lfix.co.uk/oliver
PGP: 1024R/32B8FAA1: 97 EA 1D 47 72 3F 28 47  6B 7E 39 CC 56 E4 C1 47
GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839  932A 614D 4C34 3E1D 0C1C
                 ========================================
     "I saw in the night visions, and, behold, one like the
      Son of man came with the clouds of heaven, and came to
      the Ancient of days, and they brought him near before
      him. And there was given him dominion, and glory, and
      a kingdom, that all people, nations, and languages,
      should serve him; his dominion is an everlasting
      dominion, which shall not pass away, and his kingdom
      that which shall not be destroyed."
                                    Daniel 7:13,14



Re: valid NULL DATE value

From
Peter Eisentraut
Date:
Oliver Elphick writes:

> Tony Grant wrote:
>   >Hello,
>   >
>   >I am importing via pgaccess a text file from another non-postgres
>   >database and the NULL DATE values are written like 00/00/00.
>   >
>   >What I have tried is replacing 00/00/00 by 9/9/1999 and setting the
>   >style to european and I am getting 'can't parse /9/1999' errors.
>   >
>   >How do I go about importing DATE?
>
> With INSERT, leave the field out of the list or insert NULL.
>
> With COPY, specify NULL as \N.  (You can redefine that - see COPY syntax.)

Hmm, you could use COPY ... WITH NULL AS '00/00/00', though that may spell
trouble if any non-date fields usefully contain that value.  (Probably
unlikely.)

--
Peter Eisentraut   peter_e@gmx.net   http://funkturm.homeip.net/~peter


Re: valid NULL DATE value

From
Tony Grant
Date:
Peter Eisentraut, Oliver Elphick, len morgan,

Thank you.

\N did the trick with pgaccess.

I have just cleaned up over 15000 database records in BBEdit (the data
was on a Mac server) and now ama trying to remember what I did last time
to get my accents right... When will I ever learn to take notes...

Still on schedule with this project thanks again

Tony

--
RedHat Linux on Sony Vaio C1XD/S
http://www.animaproductions.com/linux2.html
Macromedia UltraDev with PostgreSQL
http://www.animaproductions.com/ultra.html