Received: from localhost (unknown [200.46.204.183])
	by postgresql.org (Postfix) with ESMTP id CF0222E00C3
	for <pgsql-sql-postgresql.org@postgresql.org>;
	Thu, 21 Feb 2008 14:43:30 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 67632-02-4 for <pgsql-sql-postgresql.org@postgresql.org>;
	Thu, 21 Feb 2008 14:43:14 -0400 (AST)
Received: from py-out-1112.google.com (py-out-1112.google.com
 [64.233.166.178])
	by postgresql.org (Postfix) with ESMTP id 0B7412E00DE
	for <pgsql-sql@postgresql.org>; Thu, 21 Feb 2008 14:42:42 -0400 (AST)
Received: by py-out-1112.google.com with SMTP id d37so205929pye.29
	for <pgsql-sql@postgresql.org>; Thu, 21 Feb 2008 10:42:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
	bh=dnHOmHd1ErsjMLz1ZyAiHDg8uDAmKjtlJXbTxpCoveU=;
	b=ZgR7wt9yXRIbVW4uv+8iwp/3gp6x2OOVzRdPqzXm43sjyYusoI/4KR6WGpgCRR/Sas7cJNQ+xVFSPwvAv4uHbrN7FF2Cnnl5HdIZpnYVOJ/Wvx6E03Wks0zwsxbHYiwDwNH3TRDapCgFrmzQ82goZh1ro0tAbKRyMOBgsqcdkHQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
	b=PVhv2kkUwiRYjZ4B5wjFXq9p3Re2uazk8AH8b8Go9tjnV9H8qAG/MRBfPFkdSAtTNV6n9g5NLwglsJJ4Rx5tVSHPxFtDTSQmELHQgWia8Ek4w45fE+p8SbNKiYIbnw9YIKsEdPaFKjo1JbVXP7+7M9o3zp0mMwBf/Vp5YgzMoVI=
Received: by 10.65.133.8 with SMTP id k8mr20127421qbn.58.1203619361623;
	Thu, 21 Feb 2008 10:42:41 -0800 (PST)
Received: by 10.64.242.15 with HTTP; Thu, 21 Feb 2008 10:42:41 -0800 (PST)
Message-ID: <8078a1730802211042y35ea99bend21914ee2e330f00@mail.gmail.com>
Date: Thu, 21 Feb 2008 10:42:41 -0800
From: "Medi Montaseri" <montaseri@gmail.com>
To: "Sebastian Rychter" <srychter@anvet.com.ar>
Subject: Re: Data layer migration from MSSQL
Cc: pgsql-sql@postgresql.org
In-Reply-To: <008801c874b1$d468cad0$7d3a6070$@com.ar>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_5803_30306452.1203619361587"
References: <008801c874b1$d468cad0$7d3a6070$@com.ar>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200802/154
X-Sequence-Number: 30245

------=_Part_5803_30306452.1203619361587
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I think the grammer should help the parser to determine what you mean when
the token ORDER is seen.

for example in a select statement...

Syntax:
SELECT expression [, ...]
    ...
    [ FROM from_item [, ...] ]
    [ WHERE condition ]
    ...
    [ ORDER BY expression [ ASC | DESC | USING operator ]

keywords (or reserved words) should not be placed in quotes because the
parser relies on them to steer ...

Cheers
Medi

On Thu, Feb 21, 2008 at 9:47 AM, Sebastian Rychter <srychter@anvet.com.ar>
wrote:

>  Hi, I'm working on migrating a data layer from MS SQL Server to
> PostgreSQL 8.2 and found that some reserved words should only be written
> between quotes and thus are case sensitive (actually only happened with a
> table field named "order"). Is there any way to bypass this  case
> sensitivity or at least determine that I am going to use certain reserved
> words as table fields (or any other possible solutions) ?
>
>
>
> Thanks,
>
>
>
> Sebastian
>

------=_Part_5803_30306452.1203619361587
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I think the grammer should help the parser to determine what you mean when the token ORDER is seen. <br><br>for example in a select statement...<br><br>Syntax:<br>SELECT expression [, ...] <br>&nbsp;&nbsp;&nbsp; ...<br>&nbsp;&nbsp;&nbsp; [ FROM from_item [, ...] ]<br>
&nbsp;&nbsp;&nbsp; [ WHERE condition ]<br>&nbsp;&nbsp;&nbsp; ...<br>&nbsp;&nbsp;&nbsp; [ ORDER BY expression [ ASC | DESC | USING operator ]<br><br>keywords (or reserved words) should not be placed in quotes because the parser relies on them to steer ... <br><br>Cheers<br>
Medi<br><br><div class="gmail_quote">On Thu, Feb 21, 2008 at 9:47 AM, Sebastian Rychter &lt;<a href="mailto:srychter@anvet.com.ar">srychter@anvet.com.ar</a>&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">









<div link="blue" vlink="purple" lang="ES">

<div>

<p><span lang="EN-US">Hi, I'm working on migrating a data layer
from MS SQL Server to PostgreSQL 8.2 and found that some reserved words should
only be written between quotes and thus are case sensitive (actually only happened
with a table field named "order"). Is there any way to bypass this &nbsp;case
sensitivity or at least determine that I am going to use certain reserved words
as table fields (or any other possible solutions) ?</span></p>

<p><span lang="EN-US">&nbsp;</span></p>

<p><span lang="EN-US">Thanks,</span></p>

<p><span lang="EN-US">&nbsp;</span></p><font color="#888888">

<p><span lang="EN-US">Sebastian</span></p>

</font></div>

</div>


</blockquote></div><br>

------=_Part_5803_30306452.1203619361587--