| From: | Peter Eisentraut <e99re41(at)DoCS(dot)UU(dot)SE> |
|---|---|
| To: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Postgres Hackers List <hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] Date/time types: big changeu |
| Date: | 2000-02-18 14:29:34 |
| Message-ID: | Pine.GSO.4.02A.10002181524230.4777-100000@Krokodil.DoCS.UU.SE |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 17 Feb 2000, Thomas Lockhart wrote:
> However, istm that we could/should have more "default settings"
> traveling in the pg_database table. We've got the encoding, which if
> set for template1 will be set for every db. We've got the database
> location, which can point to an alternate location.
I don't think this should be a per database setting. Why not use an
environment variable PGDATESTYLE for it. That's easy enough for now.
Before we throw all kinds of per database defaults around, I'd like to see
some sort of a concept where exactly a "database" stands versus "schema",
etc. What happens if one day queries across databases are allowed?
> For v7.1, I'm hoping to work with Tatsuo and others to get closer to
> the general character sets and collation sequences allowed by SQL92.
Excellent.
--
Peter Eisentraut Sernanders vaeg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2000-02-18 14:47:05 | Re: [HACKERS] create database doesn't work well in MULTIBYTE mode |
| Previous Message | Peter Eisentraut | 2000-02-18 14:23:05 | Re: [HACKERS] psql and Control-C |