Re: [Solved] SQL Server to PostgreSQL - Mailing list pgsql-general

From Jeffrey A. Rhines
Subject Re: [Solved] SQL Server to PostgreSQL
Date
Msg-id 39A2CF21.BA68B588@email.com
Whole thread Raw
In response to Re: [Solved] SQL Server to PostgreSQL  (Tressens Lionel <tressens@etud.insa-tlse.fr>)
Responses Re: [Solved] SQL Server to PostgreSQL  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
I've wondered that myself, actually.  What are the benefits and
drawbacks to going with one over the other, besides the obvious 255-char
field length limit for varchar?  The reason to stay away from "memo"
fields in other serious RDBMSs are typically more difficult maintenance,
significantly lower performance, and requiring special function calls to
get the data out.  Do any of those apply to PG?

Jeff

Tom Lane wrote:
>
> Tressens Lionel <tressens@etud.insa-tlse.fr> writes:
> > Le 22.08.00 a 09:37, "Roderick A. Anderson" m'ecrivait :
> > )I was able to get the table format by using MS Access.  Only question left
> > )is what is the corresponding field type in PostgreSQL for a memo field in
> > )SQL Server/Access (varchar(nnnn))?
>
> > 'text' type perhaps ?
>
> Uh ... what's wrong with varchar(n) ?
>
>                         regards, tom lane

pgsql-general by date:

Previous
From: Vince Vielhaber
Date:
Subject: Re: [Solved] SQL Server to PostgreSQL
Next
From: Ned Lilly
Date:
Subject: Re: Great Bridge re-runs benchmark with MySQL "tuned"