Re: configure datatype name > 31?
| От | Mark McEahern |
|---|---|
| Тема | Re: configure datatype name > 31? |
| Дата | |
| Msg-id | NCBBLFCOHHDIKCAFGCFBKEGOKOAA.marklists@mceahern.com обсуждение исходный текст |
| Ответ на | configure datatype name > 31? ("Mark McEahern" <mark@mceahern.com>) |
| Список | pgsql-admin |
Sorry, this is a duplicate sent before I subscribed to the group--it was stalled, so I resent after subscribing. This question has been answered. Thanks, // mark > -----Original Message----- > From: pgsql-admin-owner@postgresql.org > [mailto:pgsql-admin-owner@postgresql.org]On Behalf Of Mark McEahern > Sent: Friday, May 03, 2002 10:12 AM > To: pgsql-admin@postgresql.org > Subject: [ADMIN] configure datatype name > 31? > > > Hi, the name datatype, which is used at least here: > > pg_database.datname > pg_shadow.usename > > is a 31 character field. That seems awfully low. For instance, > what if I'm > silly enough to want to make a database named: > > customer_GUID > > where GUID is something like: > > 0ff7d0cc-7394-4b15-a28e-7018b1056f9c > > You can imagine I have many customers, each with their own > database; since I > use a guid to distinguish the customers, it makes most sense to > me to use a > guid to distinguish their databases. > > Since GUIDs (in that form at least) are 36 characters, I'm already SOL. I > can condense the data, but I'd really much rather just use it like it is. > > SQL Server 2000, for example, uses nvarchar(256) for the sysname field, > which seems to perform a similar function. > > Is there a way to configure PostgreSQL to make the name field larger? > > Thanks, > > // mark > > > ---------------------------(end of broadcast)--------------------------- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly > >
В списке pgsql-admin по дате отправления: