You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Rick Hillegas <ri...@oracle.com> on 2011/06/01 15:12:07 UTC
Re: Question on a new reserved word maybe?
Hi Brett,
This bug is fixed now in all branches back through 10.6. If you build
the head of the 10.8 branch, you should be able to test-drive the fix.
Regards,
-Rick
On 5/31/11 10:32 AM, Bergquist, Brett wrote:
> Thanks.
>
> -----Original Message-----
> From: Rick Hillegas [mailto:rick.hillegas@oracle.com]
> Sent: Tuesday, May 31, 2011 1:31 PM
> To: derby-dev@db.apache.org
> Subject: Re: Question on a new reserved word maybe?
>
> Hi Brett,
>
> I will port the fix to the 10.8 branch. Then you just need to build the
> product jars according to the instructions here:
> http://db.apache.org/derby/dev/derby_source.html#How+to+build+Derby The
> real core of the process is documented here:
> http://svn.apache.org/viewvc/db/derby/code/trunk/BUILDING.html?view=co
>
> Hope this helps,
> -Rick
>
> On 5/31/11 9:25 AM, Bergquist, Brett wrote:
>> What would the procedure be to apply the change necessary and build my own build of derby 10.8.2.1 with this fix? It may not be possible to change the product that relies on this keyword (an old version of Jasper Server).
>>
>> -----Original Message-----
>> From: Rick Hillegas [mailto:rick.hillegas@oracle.com]
>> Sent: Tuesday, May 31, 2011 12:07 PM
>> To: derby-dev@db.apache.org
>> Subject: Re: Question on a new reserved word maybe?
>>
>> I have logged DERBY-5254 to track this issue.
>>
>> Thanks again for finding it,
>> -Rick
>>
>> On 5/31/11 8:15 AM, Bergquist, Brett wrote:
>>> We had been using Derby 10.5.3.1 and just upgrade to 10.8.2.1 and a
>>> DDL statement that used to work in Derby 10.5.3.1 no longer works and
>>> complains about a syntax error . Here is the statement:
>>>
>>> create table JIDataType ( id bigint not null, type smallint, maxLength
>>> integer, decimals integer, regularExpr varchar(255), minValue
>>> varchar(255) for bit data, maxValue varchar(255) for bit data,
>>> strictMin smallint, strictMax smallint, primary key (id) )
>>>
>>> and here is the error:
>>>
>>> Error: Syntax error: Encountered "minValue" at line 1, column 125.
>>>
>>> SQLState: 42X01
>>>
>>> ErrorCode: -1
>>>
>>> So did "minValue" become a reserved word? I cannot find anything like
>>> that in the documentation.
>>>
>>> Thanks for any help.
>>>
>>> Brett
>>>
>>
>>
>
>
>
Re: Question on a new reserved word maybe?
Posted by Rick Hillegas <ri...@oracle.com>.
On 6/1/11 6:32 AM, Bergquist, Brett wrote:
> Thanks Rick. I will try to build using the instructions given. This will give me good experience to build Derby and maybe contribute something over the next few months.
Let us know if you have suggestions for how to improve the build. First
impressions are very useful here.
> I am looking into the replication area and have a few ideas for some improvements that I could use.
Good to hear!
Thanks,
-Rick
> -----Original Message-----
> From: Rick Hillegas [mailto:rick.hillegas@oracle.com]
> Sent: Wednesday, June 01, 2011 9:12 AM
> To: derby-dev@db.apache.org
> Subject: Re: Question on a new reserved word maybe?
>
> Hi Brett,
>
> This bug is fixed now in all branches back through 10.6. If you build
> the head of the 10.8 branch, you should be able to test-drive the fix.
>
> Regards,
> -Rick
>
> On 5/31/11 10:32 AM, Bergquist, Brett wrote:
>> Thanks.
>>
>> -----Original Message-----
>> From: Rick Hillegas [mailto:rick.hillegas@oracle.com]
>> Sent: Tuesday, May 31, 2011 1:31 PM
>> To: derby-dev@db.apache.org
>> Subject: Re: Question on a new reserved word maybe?
>>
>> Hi Brett,
>>
>> I will port the fix to the 10.8 branch. Then you just need to build the
>> product jars according to the instructions here:
>> http://db.apache.org/derby/dev/derby_source.html#How+to+build+Derby The
>> real core of the process is documented here:
>> http://svn.apache.org/viewvc/db/derby/code/trunk/BUILDING.html?view=co
>>
>> Hope this helps,
>> -Rick
>>
>> On 5/31/11 9:25 AM, Bergquist, Brett wrote:
>>> What would the procedure be to apply the change necessary and build my own build of derby 10.8.2.1 with this fix? It may not be possible to change the product that relies on this keyword (an old version of Jasper Server).
>>>
>>> -----Original Message-----
>>> From: Rick Hillegas [mailto:rick.hillegas@oracle.com]
>>> Sent: Tuesday, May 31, 2011 12:07 PM
>>> To: derby-dev@db.apache.org
>>> Subject: Re: Question on a new reserved word maybe?
>>>
>>> I have logged DERBY-5254 to track this issue.
>>>
>>> Thanks again for finding it,
>>> -Rick
>>>
>>> On 5/31/11 8:15 AM, Bergquist, Brett wrote:
>>>> We had been using Derby 10.5.3.1 and just upgrade to 10.8.2.1 and a
>>>> DDL statement that used to work in Derby 10.5.3.1 no longer works and
>>>> complains about a syntax error . Here is the statement:
>>>>
>>>> create table JIDataType ( id bigint not null, type smallint, maxLength
>>>> integer, decimals integer, regularExpr varchar(255), minValue
>>>> varchar(255) for bit data, maxValue varchar(255) for bit data,
>>>> strictMin smallint, strictMax smallint, primary key (id) )
>>>>
>>>> and here is the error:
>>>>
>>>> Error: Syntax error: Encountered "minValue" at line 1, column 125.
>>>>
>>>> SQLState: 42X01
>>>>
>>>> ErrorCode: -1
>>>>
>>>> So did "minValue" become a reserved word? I cannot find anything like
>>>> that in the documentation.
>>>>
>>>> Thanks for any help.
>>>>
>>>> Brett
>>>>
>>>
>>
>>
>
>
>
RE: Question on a new reserved word maybe?
Posted by "Bergquist, Brett" <BB...@canoga.com>.
Thanks Rick. I will try to build using the instructions given. This will give me good experience to build Derby and maybe contribute something over the next few months. I am looking into the replication area and have a few ideas for some improvements that I could use.
-----Original Message-----
From: Rick Hillegas [mailto:rick.hillegas@oracle.com]
Sent: Wednesday, June 01, 2011 9:12 AM
To: derby-dev@db.apache.org
Subject: Re: Question on a new reserved word maybe?
Hi Brett,
This bug is fixed now in all branches back through 10.6. If you build
the head of the 10.8 branch, you should be able to test-drive the fix.
Regards,
-Rick
On 5/31/11 10:32 AM, Bergquist, Brett wrote:
> Thanks.
>
> -----Original Message-----
> From: Rick Hillegas [mailto:rick.hillegas@oracle.com]
> Sent: Tuesday, May 31, 2011 1:31 PM
> To: derby-dev@db.apache.org
> Subject: Re: Question on a new reserved word maybe?
>
> Hi Brett,
>
> I will port the fix to the 10.8 branch. Then you just need to build the
> product jars according to the instructions here:
> http://db.apache.org/derby/dev/derby_source.html#How+to+build+Derby The
> real core of the process is documented here:
> http://svn.apache.org/viewvc/db/derby/code/trunk/BUILDING.html?view=co
>
> Hope this helps,
> -Rick
>
> On 5/31/11 9:25 AM, Bergquist, Brett wrote:
>> What would the procedure be to apply the change necessary and build my own build of derby 10.8.2.1 with this fix? It may not be possible to change the product that relies on this keyword (an old version of Jasper Server).
>>
>> -----Original Message-----
>> From: Rick Hillegas [mailto:rick.hillegas@oracle.com]
>> Sent: Tuesday, May 31, 2011 12:07 PM
>> To: derby-dev@db.apache.org
>> Subject: Re: Question on a new reserved word maybe?
>>
>> I have logged DERBY-5254 to track this issue.
>>
>> Thanks again for finding it,
>> -Rick
>>
>> On 5/31/11 8:15 AM, Bergquist, Brett wrote:
>>> We had been using Derby 10.5.3.1 and just upgrade to 10.8.2.1 and a
>>> DDL statement that used to work in Derby 10.5.3.1 no longer works and
>>> complains about a syntax error . Here is the statement:
>>>
>>> create table JIDataType ( id bigint not null, type smallint, maxLength
>>> integer, decimals integer, regularExpr varchar(255), minValue
>>> varchar(255) for bit data, maxValue varchar(255) for bit data,
>>> strictMin smallint, strictMax smallint, primary key (id) )
>>>
>>> and here is the error:
>>>
>>> Error: Syntax error: Encountered "minValue" at line 1, column 125.
>>>
>>> SQLState: 42X01
>>>
>>> ErrorCode: -1
>>>
>>> So did "minValue" become a reserved word? I cannot find anything like
>>> that in the documentation.
>>>
>>> Thanks for any help.
>>>
>>> Brett
>>>
>>
>>
>
>
>