Bugs item #2925674, was opened at 2010-01-04 10:37
Message generated for change (Tracker Item Submitted) made by mbucc
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=482468&aid=2925674&group_id=56967
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: SQL/Core
Group: Clients "candidate"
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Mark Bucciarelli (mbucc)
Assigned to: Niels Nes (nielsnes)
Summary: mclient dump fails on UTF-8 char and gives no error
Initial Comment:
This is the Nov. 09 branch, built from CVS.
The mclient -D option stops dead when it hits a field with a UTF-8 character.
In addition, the return value to the shell is zero, indicating no error.
See attached test files that create this scenario on my machine.
Note that I can run
$ cat test6.sql
just fine, so it's not something related to the locale setting for my
terminal.
(Furthermore, I believe if piping to stdout to a file, it shouldn't even
matter what the locale setting for the terminal is.)
This is a really bad one--if you are using dump for backups mclient
gives no indication that there was an error.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=482468&aid=2925674&group_id=56967
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Monetdb-bugs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/monetdb-bugs
