| From: | "Josh Berkus" <josh(at)agliodbs(dot)com> | 
|---|---|
| To: | Raphael Bauduin <raphael(at)be(dot)easynet(dot)net> | 
| Cc: | pgsql-novice(at)postgresql(dot)org | 
| Subject: | Re: text field | 
| Date: | 2002-01-29 21:35:02 | 
| Message-ID: | web-679372@davinci.ethosmedia.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-novice | 
Raphael,
> I need to put a field in a database that will hold a login for the
>  users.
> That login is rather long (it's their e-mail address) and of variable
>  length (I can't 
> change that :-).
> I thought of using the text type, but wondered what were the
>  implications in terms of
> speed and amount of data (does it use much more space than other
>  character types?)
Not in PostgreSQL.  However, you may find that some interfaces (such as
 ODBC and JDBC) put limits on waht you can do with a Text column.  For
 example, MS Access/ODBC will interpret a TEXT field (or and VARCHAR
 over 250 chars) as a "memo" field and refuse to let you search or
 aggregate on the field.
Otherwise, TEXT and VARCHAR perform the same in PostgreSQL.
-Josh Berkus
______AGLIO DATABASE SOLUTIONS___________________________
                                       Josh Berkus
  Complete information technology      josh(at)agliodbs(dot)com
   and data management solutions       (415) 565-7293
  for law firms, small businesses        fax 621-2533
    and non-profit organizations.      San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rabin Nathan | 2002-01-29 21:56:25 | [Fwd: Re: pgaccess connection problems] | 
| Previous Message | Raphael Bauduin | 2002-01-29 15:00:22 | text field |