Re: new postgres

Posted by TimJ on Mon Nov 9 9:21:01 1998

In Reply to: new postgres posted by william on November 08, 1998 at 16:01:21:

>Postgres 6.4 is out, and finally supports SERIAL (autoincrement)
>without making you jump through hoops. Also has a PL
>(procedural language) which would let one push a lot of
>logic onto the backend and therefore probably make it
>more efficient, though the problem with this is that they
>are not at all standard so you lose portability :(.

my experience with plSQL (oracle) wasn't great, although it was nice for testing. The portability argument is a strong one.

I think it is a bad idea to move code into Postgres.

Follow Ups:

• Re: Re: new postgres WilliamC pp TimJ Mon Nov 9 11:33:54 1998 (4)
  • Summary of quick investigation WilliamC Tue Nov 10 13:44:15 1998 (0)
  • feedback from postgres user 2 WilliamC Tue Nov 10 12:56:37 1998 (0)
  • feedback from postgres user 1 WilliamC Tue Nov 10 12:54:40 1998 (0)
  • Re: Re: Re: new postgres TimJ Mon Nov 9 11:35:27 1998 (0)
  
  

  ---

  Post a Followup

  Name:

  E-Mail:

  Copy:

  Circulation: AlexH ColinR DanielH JackM JennyP KeithH KrugerD MikeC MylesC NicR PatickG TimJ TimP WilliamC WilliamS paneris

  Subject:

  >>Postgres 6.4 is out, and finally supports SERIAL (autoincrement) >>without making you jump through hoops. Also has a PL >>(procedural language) which would let one push a lot of >>logic onto the backend and therefore probably make it >>more efficient, though the problem with this is that they >>are not at all standard so you lose portability :(. >my experience with plSQL (oracle) wasn't great, although it was nice for testing. The portability argument is a strong one. >I think it is a bad idea to move code into Postgres.

  ---

  [ Follow Ups ] [ Post a Followup ] [ Discussions at the Paneris newbox node ]