Re: [Solved] SQL Server to PostgreSQL

From: "Jeffrey A(dot) Rhines" <jrhines(at)email(dot)com>
To: "PostgreSQL::General List" <pgsql-general(at)postgreSQL(dot)org>
Subject: Re: [Solved] SQL Server to PostgreSQL
Date: 2000-08-22 19:06:09
Message-ID: 39A2CF21.BA68B588@email.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

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(at)etud(dot)insa-tlse(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Stephan Szabo 2000-08-22 19:09:08 Re: Foreign key to all inherited tables
Previous Message Vince Vielhaber 2000-08-22 19:02:50 Re: [Solved] SQL Server to PostgreSQL

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Hollomon 2000-08-22 19:10:19 Re: when does CREATE VIEW not create a view?
Previous Message Vince Vielhaber 2000-08-22 19:02:50 Re: [Solved] SQL Server to PostgreSQL