Bugs item #3031529, was opened at 2010-07-19 13:58 Message generated for change (Settings changed) made by shcheklein You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=713730&aid=3031529&group_id=129076
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General Group: Sedna (development) Status: Open >Resolution: Accepted >Priority: 3 Private: No Submitted By: chun chen (goodluckfish) >Assigned to: Ivan Shcheklein (shcheklein) Summary: Error SE4211 under path with 2 bytes characters Initial Comment: version of Sedna - 3.3.55 operating system version - Windows 5.1.2600 (SP3.0) x86 When trying to create a database under path with 2 bytes characters, I got the ERROR SE4211. 2 bytes characters means Chinese or Japanese characters. Command lines : E:\publish\版本发布\sedna\bin>se_gov GOVERNOR has been started in the background mode E:\publish\版本发布\sedna\bin>se_cdb aaa Creating a data base (it can take a few minutes)... SEDNA Message: ERROR SE4211 Failed to create the database Details: aaa Cannot complete cleanup. Please stop Sedna and remove the following: file - /cfg/aaa_cfg.xml folder - /data/aaa_files Sorry for inconvenience. E:\publish\版本发布\sedna\bin> ---------------------------------------------------------------------- >Comment By: Ivan Shcheklein (shcheklein) Date: 2010-07-19 16:55 Message: Hi Chun, This is a known limitation of Sedna. For the moment the only workaround is to use ASCII chars in path. Technical comments for developers for further work on this issue: 1. On windows seems we have to define UNICODE (see MSND, Conventions for Function Prototypes) and use wchar* for all system calls. Everywhere we need we should translate Sedna's UTF-8 strings (like SEDNA_DATA) -> wchar and backward. 2. On windows we should also explicitly use _wfopen instead of fopen, etc ... 3. On Linux there is no "wfopen()" (just plain old "fopen()" will suffice), but there *are* Unicode equivalents for each of the file read and write APIs. Should we use them? 4. We should also check other supported platforms - OS X, Solaris, BSD. 5. As a temporary fix probably we may raise some exception on se_gov if there are non ASCII chars? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=713730&aid=3031529&group_id=129076 ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Sedna-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sedna-discussion
