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 "Satheesh Bandaram (JIRA)" <de...@db.apache.org> on 2005/11/04 01:41:57 UTC
[jira] Commented: (DERBY-675) Build-time processing of "metadata.properties" file handles slashes incorrectly.
[ http://issues.apache.org/jira/browse/DERBY-675?page=comments#action_12356730 ]
Satheesh Bandaram commented on DERBY-675:
-----------------------------------------
This patch is committed.
Sending java\build\org\apache\derbyBuild\ODBCMetadataGenerator.java
Transmitting file data .
Committed revision 330672.
> Build-time processing of "metadata.properties" file handles slashes incorrectly.
> --------------------------------------------------------------------------------
>
> Key: DERBY-675
> URL: http://issues.apache.org/jira/browse/DERBY-675
> Project: Derby
> Type: Bug
> Components: Build tools
> Versions: 10.2.0.0, 10.1.1.1, 10.1.1.0
> Reporter: A B
> Assignee: A B
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: d675_v2.patch
>
> As found and described by Mamta here:
> http://www.nabble.com/-Derby-573-Optimizer-overrides-and-metadata.properties-files-t460642.html
> During the ant build process, Derby's metadata.properties file is modified by the ODBCMetadataGenerator class and that class treats backslashes that occur in the metadata.properties file incorrectly. More specifically, it treats every backslash as the end of a line and thus will translate things like
> FROM --DERBY-PROPERTIES joinOrder=FIXED \\n \
> into
> FROM --DERBY-PROPERTIES joinOrder=FIXED \
> \
> n \
> (in other words, escaped characters like "\n" are handled incorrectly)..
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Re: [jira] Commented: (DERBY-675) Build-time processing of "metadata.properties" file handles slashes incorrectly.
Posted by Mamta Satoor <ms...@gmail.com>.
Hi Army,
Just wanted to let you know that your fix did the trick and now I can use
\n in metadata.properties.
thanks for quick turn around in getting it resolved.
Mamta
On 11/3/05, Satheesh Bandaram (JIRA) <de...@db.apache.org> wrote:
>
> [
> http://issues.apache.org/jira/browse/DERBY-675?page=comments#action_12356730]
>
> Satheesh Bandaram commented on DERBY-675:
> -----------------------------------------
>
> This patch is committed.
>
> Sending java\build\org\apache\derbyBuild\ODBCMetadataGenerator.java
> Transmitting file data .
> Committed revision 330672.
>
>
> > Build-time processing of "metadata.properties" file handles slashes
> incorrectly.
> >
> --------------------------------------------------------------------------------
> >
> > Key: DERBY-675
> > URL: http://issues.apache.org/jira/browse/DERBY-675
> > Project: Derby
> > Type: Bug
> > Components: Build tools
> > Versions: 10.2.0.0 <http://10.2.0.0>, 10.1.1.1 <http://10.1.1.1>,
> 10.1.1.0 <http://10.1.1.0>
> > Reporter: A B
> > Assignee: A B
> > Priority: Minor
> > Fix For: 10.2.0.0 <http://10.2.0.0>
> > Attachments: d675_v2.patch
> >
> > As found and described by Mamta here:
> >
> http://www.nabble.com/-Derby-573-Optimizer-overrides-and-metadata.properties-files-t460642.html
> > During the ant build process, Derby's metadata.properties file is
> modified by the ODBCMetadataGenerator class and that class treats
> backslashes that occur in the metadata.properties file incorrectly. More
> specifically, it treats every backslash as the end of a line and thus will
> translate things like
> > FROM --DERBY-PROPERTIES joinOrder=FIXED \\n \
> > into
> > FROM --DERBY-PROPERTIES joinOrder=FIXED \
> > \
> > n \
> > (in other words, escaped characters like "\n" are handled incorrectly)..
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
> http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see:
> http://www.atlassian.com/software/jira
>
>