You are viewing a plain text version of this content. The canonical link for it is here.
Posted to slide-dev@jakarta.apache.org by bu...@apache.org on 2004/02/09 08:51:21 UTC
DO NOT REPLY [Bug 26784] New: -
Database Schema may not allow unicode in URIs
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26784>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26784
Database Schema may not allow unicode in URIs
Summary: Database Schema may not allow unicode in URIs
Product: Slide
Version: 2.0
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Stores
AssignedTo: slide-dev@jakarta.apache.org
ReportedBy: ozeigermann@c1-fse.de
Schemas for MySQL and Postgres may not allow unicode in URIs. For SQLServer this
issue has been solved
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org
Re: DO NOT REPLY [Bug 26784] New: - Database Schema may not allow
unicode in URIs
Posted by Eric Johnson <er...@tibco.com>.
This may just be a terminology quibble. We've had confusion at my
company, so I thought I'd discourage such confusion in Apache code.
A URI has a very specific character set that is allowed, a subset of
US-ASCII. Representation of non US-ASCII character is done (roughly) via
the convention of UTF-8 encoding the Unicode, then applying URL escaping
(%XX) on the resulting bytes. If it includes non-ascii characters, it
isn't a URI, by definition.
IRIs expand the URI character set to include unicode characters, where
doing so does not conflict with the syntax of URIs. This is a draft
proposal, can can be found here:
http://www.ietf.org/internet-drafts/draft-duerst-iri-05.txt
My suggestion is that if the data being represented is already decoded,
it should be called a *path*. Note that a "path", and an IRI are not
interchangeable either, even though IRIs allow Unicode. For example, in
a path, the following looks reasonable "/my folder/my file.txt", but
this isn't a valid IRI, and would instead be represented as an IRI with
"/my%20folder/my%20file.txt".
I think using the correct terminology helps to make it crystal clear
what kind of conversion is needed in what context, since all three tend
to be represented as String.
-Eric.
Jacob Lund wrote:
>I am not sure what an IRI is, but the database scheme does contain uri's!
>
>In order to support UTF-8 in URI's, I changed all text's fields in the
>database scheme to nchar and nvarchar (SQL server Unicode character). If
>this is not done the database or the driver will automatically convert all
>characters to local character set, and this will result in a problem when an
>UTF-8 encoded character is not available in the local character set.
>
>This worked for me with SQL server.
>
>/Jacob
>
>-----Original Message-----
>From: Eric Johnson [mailto:eric@tibco.com]
>Sent: 9. februar 2004 14:09
>To: Slide Developers Mailing List
>Subject: Re: DO NOT REPLY [Bug 26784] New: - Database Schema may not allow
>unicode in URIs
>
>This bug confuses me. Note that I have not looked at the database
>schemas, and don't really understand the code in question.
>
>However, URIs *never* contain Unicode. If they do, they're not URIs any
>more. Perhaps you mean IRIs?
>
>-Eric.
>
>bugzilla@apache.org wrote:
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org
RE: DO NOT REPLY [Bug 26784] New: - Database Schema may not allow unicode in URIs
Posted by Jacob Lund <jl...@qualiware.com>.
I am not sure what an IRI is, but the database scheme does contain uri's!
In order to support UTF-8 in URI's, I changed all text's fields in the
database scheme to nchar and nvarchar (SQL server Unicode character). If
this is not done the database or the driver will automatically convert all
characters to local character set, and this will result in a problem when an
UTF-8 encoded character is not available in the local character set.
This worked for me with SQL server.
/Jacob
-----Original Message-----
From: Eric Johnson [mailto:eric@tibco.com]
Sent: 9. februar 2004 14:09
To: Slide Developers Mailing List
Subject: Re: DO NOT REPLY [Bug 26784] New: - Database Schema may not allow
unicode in URIs
This bug confuses me. Note that I have not looked at the database
schemas, and don't really understand the code in question.
However, URIs *never* contain Unicode. If they do, they're not URIs any
more. Perhaps you mean IRIs?
-Eric.
bugzilla@apache.org wrote:
>DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
>RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
><http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26784>.
>ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
>INSERTED IN THE BUG DATABASE.
>
>http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26784
>
>Database Schema may not allow unicode in URIs
>
> Summary: Database Schema may not allow unicode in URIs
> Product: Slide
> Version: 2.0
> Platform: Other
> OS/Version: Other
> Status: NEW
> Severity: Normal
> Priority: Other
> Component: Stores
> AssignedTo: slide-dev@jakarta.apache.org
> ReportedBy: ozeigermann@c1-fse.de
>
>
>Schemas for MySQL and Postgres may not allow unicode in URIs. For SQLServer
this
>issue has been solved
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: slide-dev-help@jakarta.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org
Re: DO NOT REPLY [Bug 26784] New: - Database Schema may not allow
unicode in URIs
Posted by Eric Johnson <er...@tibco.com>.
This bug confuses me. Note that I have not looked at the database
schemas, and don't really understand the code in question.
However, URIs *never* contain Unicode. If they do, they're not URIs any
more. Perhaps you mean IRIs?
-Eric.
bugzilla@apache.org wrote:
>DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
>RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
><http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26784>.
>ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
>INSERTED IN THE BUG DATABASE.
>
>http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26784
>
>Database Schema may not allow unicode in URIs
>
> Summary: Database Schema may not allow unicode in URIs
> Product: Slide
> Version: 2.0
> Platform: Other
> OS/Version: Other
> Status: NEW
> Severity: Normal
> Priority: Other
> Component: Stores
> AssignedTo: slide-dev@jakarta.apache.org
> ReportedBy: ozeigermann@c1-fse.de
>
>
>Schemas for MySQL and Postgres may not allow unicode in URIs. For SQLServer this
>issue has been solved
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: slide-dev-help@jakarta.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org