Skip site navigation (1) Skip section navigation (2)

Bug #766: version difference creates problem

From: pgsql-bugs(at)postgresql(dot)org
To: pgsql-bugs(at)postgresql(dot)org
Subject: Bug #766: version difference creates problem
Date: 2002-09-14 13:02:32
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
Pranav Vora (pranav(at)babultech(dot)com) reports a bug with a severity of 2
The lower the number the more severe it is.

Short Description
version difference creates problem

Long Description

I am using Postgres 6.5 on Redhat 6.2 and postgres 7.0 on Redhat 7.0/Mandrake 8.0 perfectly. And, I was running my web application since 1.5 years.

Now, when I tried  to run my web application on Mandrake 8.1 with Postgres 7.1.2. It is the staring point of creating problems. When I trace back the problem, I found that 'inout' is creating problem.

I have a database table named 'inout'.So, from previous version I dumped database through pg_dump and created one .db file.

Then I re-created on 7.1.2 through psql and then \i command. It was successfull. Then other tables were accessed without pain. 

select * from inout; was giving parse error near or at 'inout'

Then I juggled with query and found that

select * from "inout" is working. but, such thing can not be done in my web application as it is a java code and I can't afford to change all the queries with table name change thoroughout the system.

So, please, help me out as early as possible, because,it's a time management system so each day is important

waiting for your favourable reply...


Sample Code

No file was uploaded with this report


pgsql-bugs by date

Next:From: Peter EisentrautDate: 2002-09-14 13:52:24
Subject: Re: Bug #765: 'IS NULL' versus '= NULL'
Previous:From: Hubert depesz LubaczewskiDate: 2002-09-14 12:08:00
Subject: Re: Bug #765: 'IS NULL' versus '= NULL'

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group