Re: Column does not exists?

From: Francisco Olarte <folarte(at)peoplecall(dot)com>
To: Leonardo M(dot) Ramé <l(dot)rame(at)griensu(dot)com>
Cc: PostgreSql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Column does not exists?
Date: 2015-03-26 17:57:17
Message-ID: CA+bJJbyvMFLNiSvjjqm8c8MPeC+eYw6P6t_8AHefFNZjKJOTwA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi Leonardo:

> Aha, the problem, then, was caused by the Create statement. This table was
> copied from a MySql dump where all columns were named "column".

In part. The problem was caused by non-uniform quote usaga, quotes in
create, no quotes elsewhere.

Had you used quotes in delete or not used quotes in create everything
would have go well. You can try to game the system, but it'e easier if
you use them always or never, and always use the same case. I mean,
create table "a", delete from A may work in postgres but fail in other
db . create a, delete A normally works everywhere ( case folding, in
either direction, but you are asking for problems if you decide to
quote identifiers for any reason ), and create "a" delete "A" should
fail everywhere.

Francisco Olarte.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Timothy Garnett 2015-03-26 20:49:51 Creating a non-strict custom aggregate that initializes to the first value
Previous Message Andreas Kretschmer 2015-03-26 17:53:22 Re: 9.4+ partial log-shipping possible?