From srychter@anvet.com.ar Thu Feb 21 17:47:43 2008 Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 458D02E0093 for ; Thu, 21 Feb 2008 13:47:43 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 43363-01-2 for ; Thu, 21 Feb 2008 13:47:32 -0400 (AST) Received: from server2.dns-principal-3.com (server2.dns-principal-3.com [66.7.198.76]) by postgresql.org (Postfix) with ESMTP id 1AB112E00C8 for ; Thu, 21 Feb 2008 13:47:32 -0400 (AST) Received: from [201.231.212.172] (helo=brainmart05) by server2.dns-principal-3.com with esmtpa (Exim 4.68) (envelope-from ) id 1JSFW5-0006s4-BW; Thu, 21 Feb 2008 12:47:29 -0500 From: "Sebastian Rychter" To: Subject: Data layer migration from MSSQL Date: Thu, 21 Feb 2008 15:47:26 -0200 Message-ID: <008801c874b1$d468cad0$7d3a6070$@com.ar> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0089_01C874A1.10DFFAD0" X-Mailer: Microsoft Office Outlook 12.0 Thread-index: Ach0sdHWVGXaBHY+TKeqz1Ot0sa5pQ== Content-Language: es X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - server2.dns-principal-3.com X-AntiAbuse: Original Domain - postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - anvet.com.ar X-Source: X-Source-Args: X-Source-Dir: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=AWL=-0.001, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200802/153 X-Sequence-Number: 30244 Este es un mensaje con varias partes en formato MIME. ------=_NextPart_000_0089_01C874A1.10DFFAD0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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 ------=_NextPart_000_0089_01C874A1.10DFFAD0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

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

------=_NextPart_000_0089_01C874A1.10DFFAD0-- From montaseri@gmail.com Thu Feb 21 18:43:30 2008 Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id CF0222E00C3 for ; 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 ; 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 ; Thu, 21 Feb 2008 14:42:42 -0400 (AST) Received: by py-out-1112.google.com with SMTP id d37so205929pye.29 for ; 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" To: "Sebastian Rychter" 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 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.

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-- From srychter@anvet.com.ar Thu Feb 21 18:56:27 2008 Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 5FB582E009F for ; Thu, 21 Feb 2008 14:56:27 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 10608-01-9 for ; Thu, 21 Feb 2008 14:56:13 -0400 (AST) Received: from server2.dns-principal-3.com (server2.dns-principal-3.com [66.7.198.76]) by postgresql.org (Postfix) with ESMTP id DCB2F2E0080 for ; Thu, 21 Feb 2008 14:55:53 -0400 (AST) Received: from [201.231.212.172] (helo=brainmart05) by server2.dns-principal-3.com with esmtpa (Exim 4.68) (envelope-from ) id 1JSGa3-0001kt-0x; Thu, 21 Feb 2008 13:55:41 -0500 From: "Sebastian Rychter" To: "'Medi Montaseri'" Cc: References: <008801c874b1$d468cad0$7d3a6070$@com.ar> <8078a1730802211042y35ea99bend21914ee2e330f00@mail.gmail.com> In-Reply-To: <8078a1730802211042y35ea99bend21914ee2e330f00@mail.gmail.com> Subject: Re: Data layer migration from MSSQL Date: Thu, 21 Feb 2008 16:55:35 -0200 Message-ID: <00cb01c874bb$5a230510$0e690f30$@com.ar> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00CC_01C874AA.969A3510" X-Mailer: Microsoft Office Outlook 12.0 Thread-index: Ach0uYsCmy8vXrIZRimiwBPYLLJjewAAJdLA Content-Language: es X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - server2.dns-principal-3.com X-AntiAbuse: Original Domain - postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - anvet.com.ar X-Source: X-Source-Args: X-Source-Dir: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=AWL=-0.000, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200802/155 X-Sequence-Number: 30246 Este es un mensaje con varias partes en formato MIME. ------=_NextPart_000_00CC_01C874AA.969A3510 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sorry, I think it was misunderstood. I meant that I used the keyword = =E2=80=9COrder=E2=80=9D as a table property, not as part as the = statement In MS SQL I use [Order] and then just query :=20 =20 Select [Table1].[Order] from [Table1]=20 =20 Or=20 =20 Select [Table1].[order] from [Table1] =20 In Postgresql I can=E2=80=99t do : create table Table1 (order = varchar(10)) -- because =E2=80=9Corder=E2=80=9D is a keyword I have to do it like : create Table1 (=E2=80=9COrder=E2=80=9D = varchar(10)) And then always do the query like : Select =E2=80=9COrder=E2=80=9D from = Table1=20 which is different from=20 = Select =E2=80=9Corder=E2=80=9D from Table1 =20 Thanks again. =20 De: Medi Montaseri [mailto:montaseri@gmail.com]=20 Enviado el: jueves, 21 de febrero de 2008 16:43 Para: Sebastian Rychter CC: pgsql-sql@postgresql.org Asunto: Re: [SQL] Data layer migration from MSSQL =20 I think the grammer should help the parser to determine what you mean = when the token ORDER is seen.=20 for example in a select statement... Syntax: SELECT expression [, ...]=20 ... [ 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 ...=20 Cheers Medi On Thu, Feb 21, 2008 at 9:47 AM, Sebastian Rychter = 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) ? =20 Thanks, =20 Sebastian =20 ------=_NextPart_000_00CC_01C874AA.969A3510 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Sorry,=C2=A0 I think it was misunderstood. I meant that I = used the keyword =E2=80=9COrder=E2=80=9D as a table property, not as part as the = statement

In MS SQL I use [Order] and then just query : =

Select [Table1].[Order] from [Table1]

Or

Select [Table1].[order] from [Table1]

In Postgresql I can=E2=80=99t do : create table Table1 = (order varchar(10))=C2=A0 -- because =E2=80=9Corder=E2=80=9D is a keyword

I have to do it like : create Table1 = (=E2=80=9COrder=E2=80=9D varchar(10))

And then always do the query like : Select = =E2=80=9COrder=E2=80=9D from Table1

which is different from

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Select =E2=80=9Corder=E2=80=9D from Table1

Thanks again.

De: Medi = Montaseri [mailto:montaseri@gmail.com]
Enviado el: jueves, 21 de febrero de 2008 16:43
Para: Sebastian Rychter
CC: pgsql-sql@postgresql.org
Asunto: Re: [SQL] Data layer migration from = MSSQL

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

------=_NextPart_000_00CC_01C874AA.969A3510--