Thread: [HACKERS] Database Restore with 6.1 fails (Name -> name).
Greetings. I just built 6.1 on a Linux 2.0.29 (RedHat) machine, following the instructions to the letter. Everything looked fine until I went to access one of my databases. Some of them seem to be fine, but others have had the field names converted to all lower-case. When I dropped the table and re-created it, it still ended up with the field turned into lower case. I dumped the database with the dumpall command and restored as suggested in the installation instructions. Here's a sample session: xvscanpub=> CREATE TABLE ProjUser (Key int4, Name text) archive = none; CREATE xvscanpub=> COPY ProjUser WITH OIDS FROM stdin; Enter info followed by a newline End with a backslash and a period on a line by itself. >> 513147 1 jafo >> 513148 2 efm >> \. resetting connection xvscanpub=> select * from ProjUser; key|name ---+---- (0 rows) I backed off to 6.0, but wanted to send in a report. Other than that, it looked fine... Sean - -- Do bad programmers wake up on Christmas morning to find coal in their sockets? -- Sean Reifschneider Sean Reifschneider, Inimitably Superfluous <jafo@tummy.com> URL: <http://www.tummy.com/xvscan> HP-UX/Linux/FreeBSD/BSDOS scanning software. ------------------------------
On Sun, 15 Jun 1997, Sean Reifschneider wrote:
> Greetings. I just built 6.1 on a Linux 2.0.29 (RedHat) machine, following
> the instructions to the letter. Everything looked fine until I went
> to access one of my databases. Some of them seem to be fine, but others
> have had the field names converted to all lower-case. When I dropped the
> table and re-created it, it still ended up with the field turned into
> lower case.
>
> I dumped the database with the dumpall command and restored as suggested
> in the installation instructions. Here's a sample session:
>
> xvscanpub=> CREATE TABLE ProjUser (Key int4, Name text) archive = none;
> CREATE
> xvscanpub=> COPY ProjUser WITH OIDS FROM stdin;
> Enter info followed by a newline
> End with a backslash and a period on a line by itself.
> >> 513147 1 jafo
> >> 513148 2 efm
> >> \.
> resetting connection
> xvscanpub=> select * from ProjUser;
> key|name
> ---+----
> (0 rows)
>
> I backed off to 6.0, but wanted to send in a report. Other than that,
> it looked fine...
Case sensitivity in tables/field names were removed in v6.1...
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
------------------------------
>
> Case sensitivity in tables/field names were removed in v6.1...
If one wants case sensitivity how do yo get it?
TIA
Wayne
>
> Marc G. Fournier
> Systems Administrator @ hub.org
> primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
>
>
------------------------------
On Sun, 15 Jun 1997, wward wrote:
> >
> > Case sensitivity in tables/field names were removed in v6.1...
>
> If one wants case sensitivity how do yo get it?
Run v6.0...there is no on/off switch to it...there was a major
discussion about 3 months ago as to whether we should keep it or not, and
the conscencous(sp?) was no...
If I recall the arguments correctly, case sensitivity broke all the
ODBC and JDBC drivers :(
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
------------------------------
>
> >
> > Case sensitivity in tables/field names were removed in v6.1...
>
> If one wants case sensitivity how do yo get it?
You stay with 6.0. You can try removing the case-insensitivity code in
the {identifier} section of backend/parser/scan.l, but there are other
areas that do this too.
- --
Bruce Momjian
maillist@candle.pha.pa.us
------------------------------
On Sun, Jun 15, 1997 at 10:24:42PM -0300, The Hermit Hacker wrote: >On Sun, 15 Jun 1997, wward wrote: >> > Case sensitivity in tables/field names were removed in v6.1... >> >> If one wants case sensitivity how do yo get it? > > If I recall the arguments correctly, case sensitivity broke all the >ODBC and JDBC drivers :( My problem was that I forgot to re-compile my apache server (which has PHP, which is the reason I'm using Postgres) with the new libpq. However, I suspect that the Java Postgres class is going to require patches to do a string insensitive compare -- it doesn't use libpq. I can deal with re-building all my programs, I guess... I'll probably just leave my main server running the old version for now. Actually, I think it's better to be case insensitive, but doing it now is kind of a pain. It'll be more of one if it happened later though... Sean - -- "We've secretly replaced the Dilithium Crystals on these starships with Folger's. Let's see if they can tell the difference." -- Sean and Anne Sean Reifschneider, Inimitably Superfluous <jafo@tummy.com> URL: <http://www.tummy.com/xvscan> HP-UX/Linux/FreeBSD/BSDOS scanning software. ------------------------------ End of hackers-digest V1 #388 *****************************