Return-Path: X-Original-To: apmail-db-derby-user-archive@www.apache.org Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 24B3C1179B for ; Sat, 19 Apr 2014 01:35:23 +0000 (UTC) Received: (qmail 16915 invoked by uid 500); 19 Apr 2014 01:35:22 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 16878 invoked by uid 500); 19 Apr 2014 01:35:22 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 16871 invoked by uid 99); 19 Apr 2014 01:35:21 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 19 Apr 2014 01:35:21 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of meyerjp3@gmail.com designates 209.85.216.175 as permitted sender) Received: from [209.85.216.175] (HELO mail-qc0-f175.google.com) (209.85.216.175) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 19 Apr 2014 01:35:15 +0000 Received: by mail-qc0-f175.google.com with SMTP id e16so2244517qcx.20 for ; Fri, 18 Apr 2014 18:34:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:mime-version:content-type :thread-index:content-language; bh=HRoUPSvaZod9FYKfUd/TEhEq/INQnpv2jRS+mdqhpRM=; b=OwPPn++3geOewMIo2sm2ScuwNtS5xNUUu2NmpEILjHO2OPzEHizSwqqYNigG00H75v sOk9UZzhbbBwdBsxZKXa6gNvM49IL/k0bt4OJh5hnmmAcf0mixfXzsmmHcVWKJxsvl+X e3Gn18E+WYvBqE9iMWJQrfZ8ep/T7U8XY4zFlVVMlGu9GDqS1jCD9x92TnzxCYU3iVTj R/Vd7ffLxptmByESPNmNFCaDF0VKlKs1eV4PwCObbbqID2xBvl+GxlQuDr9e7gINeAYH X5YWorAjdjPY0xttXN5gP7s9C2wEgxqLyE/a9IPw+Ol2CDXIAjqSQVu98tePB7jCXyH6 dsAw== X-Received: by 10.224.61.200 with SMTP id u8mr24727259qah.18.1397871292883; Fri, 18 Apr 2014 18:34:52 -0700 (PDT) Received: from R2D2 (c-98-249-58-20.hsd1.va.comcast.net. [98.249.58.20]) by mx.google.com with ESMTPSA id m2sm58856986qac.3.2014.04.18.18.34.52 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 18 Apr 2014 18:34:52 -0700 (PDT) From: "Patrick Meyer" To: Subject: CREATE TABLE lexical error Date: Fri, 18 Apr 2014 21:34:53 -0400 Message-ID: <002101cf5b6f$904bd4e0$b0e37ea0$@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0022_01CF5B4E.093D1B10" X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac9bbt+TkG8rlA+kRRKTXKwKvk9jlg== Content-Language: en-us X-Virus-Checked: Checked by ClamAV on apache.org This is a multipart message in MIME format. ------=_NextPart_000_0022_01CF5B4E.093D1B10 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I have an application that allows users to import data into Derby. As = such, the users specify the column names. A user encountered a lexical = error message that I have been able to reproduce with the following = CREATE TABLE statements. Can anyone explain why the column names appear = to be causing a lexical error and how to avoid it? I am using 10.9.1. =20 These two statements result in errors: =20 CREATE TABLE TBLPAT1 (x=EF=BB=BFb1x DOUBLE, xb2x DOUBLE)=20 Error: Lexical error at line 1, column 24. Encountered: "\ufeff" = (65279), after : "". =20 CREATE TABLE TBLPAT2 (x=EF=BB=BFb1x VARCHAR(50), xb2x VARCHAR(50))=20 Error: Lexical error at line 1, column 24. Encountered: "\ufeff" = (65279), after : "". SQLState: 42X02 ErrorCode: 30000 =20 =20 These statements work just fine. =20 CREATE TABLE TBLPAT3 (xvar1x DOUBLE, xvar2x DOUBLE)=20 =20 CREATE TABLE TBLPAT4 (xvar1x VARCHAR(50), xvar2x DOUBLE)=20 =20 CREATE TABLE TBLPAT5 (xvar1x VARCHAR(50), xvar2x VARCHAR(50)) =20 =20 Thanks, Patrick =20 ------=_NextPart_000_0022_01CF5B4E.093D1B10 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

I have an = application that allows users to import data into Derby. As such, the = users specify the column names. A user encountered a lexical error = message that I have been able to reproduce with the following CREATE = TABLE statements. Can anyone explain why the column names appear to be = causing a lexical error and how to avoid it? I am using = 10.9.1.

 

These two statements result in = errors:

 

CREATE TABLE TBLPAT1 (x=EF=BB=BFb1x DOUBLE, xb2x = DOUBLE)

Error: Lexical error at line = 1, column 24.=C2=A0 Encountered: "\ufeff" (65279), after : = "".

 

CREATE TABLE TBLPAT2 (x=EF=BB=BFb1x VARCHAR(50), xb2x = VARCHAR(50))

Error: Lexical error at = line 1, column 24.=C2=A0 Encountered: "\ufeff" (65279), after = : "".

SQLState:=C2=A0 = 42X02

ErrorCode: = 30000

 

 

These = statements work just fine.

 

CREATE TABLE = TBLPAT3 (xvar1x DOUBLE, xvar2x DOUBLE)

 

CREATE TABLE = TBLPAT4 (xvar1x VARCHAR(50), xvar2x DOUBLE)

 

CREATE TABLE = TBLPAT5 (xvar1x VARCHAR(50), xvar2x VARCHAR(50))

 

 

Thanks,

Patrick

 

------=_NextPart_000_0022_01CF5B4E.093D1B10--