Re: Problems on "copy" statement

From: "Keith Worthington" <keithw(at)narrowpathinc(dot)com>
To: Michael Fuhr <mike(at)fuhr(dot)org>
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: Problems on "copy" statement
Date: 2005-04-13 16:36:09
Message-ID: 20050413161747.M82458@narrowpathinc.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

On Wed, 13 Apr 2005 09:34:42 -0600, Michael Fuhr wrote
> On Wed, Apr 13, 2005 at 10:38:02AM -0400, Keith Worthington wrote:
> > On Wed, 13 Apr 2005 22:29:05 +0800, Leung Wing Lap Ellery wrote
> > >
> > > copy hsi from 'c:\java\hsi.txt'
> > >
> > > it generated error:
> > >
> > > ERROR: relation "hsi" does not exist
> > > copy hsi from 'c:\java\hsi.txt'
> >
> > It seems to me that it cannot find the table. Try schema qualifying the
> > tablename.
>
> Another possibility is that the table name is mixed-case -- if so,
> then it'll have to be quoted.
>
> http://www.postgresql.org/docs/8.0/interactive/sql-syntax.html#SQL-
> SYNTAX-IDENTIFIERS
>
> What's the result of the following query?
>
> SELECT schemaname, tablename
> FROM pg_tables
> WHERE tablename ILIKE '%hsi%';
>
> --
> Michael Fuhr

To quote my kids; "Yikers!" :-)

I vaguely remember colliding with case sensitivity in 7.3.X when I first
started using postgresql. I changed all my table and column names to
lowercase to avoid the issue and I haven't thought about it since. That
appears to be changed in 8.0.0 as SELECT * FROM myschema.tbl_name; and SELECT
* FROM MySchema.Tbl_Name; work equally well. Is this a new supported now and
forever behavior? IT would be nice for readability and compactness to be able
to use SalesOrder.TblDetail.ItemID instead of sales_order.tbl_detail.item_id.

Kind Regards,
Keith

In response to

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message Sean Davis 2005-04-13 16:37:01 Re: Problems on "copy" statement
Previous Message Leung Wing Lap Ellery 2005-04-13 16:24:42 Re: Problems on "copy" statement