FROM : Ondra Cada
DATE : Wed Jul 26 16:30:02 2006
Hello mmalc and all,
I've bumped into a CoreData bug, which self-evidently is related to
its XML generator and/or parser. Here's a simple repeat procedure:
(i) take the standard Apple example /Developer/Examples/CoreData/
EventManager
(ii) build the thing and launch
(iii) create a new event, name it
"#990000"><
(incl. quote marks), set some dates, save using XML format, close
(iv) reopen the file. The name is now '"#990000"><󱬰"><'.
Is this a known bug? More important, is there a known work-around?
Searching Cocoabuilder I've found just http://www.cocoabuilder.com/
archive/message/cocoa/2005/10/12/147940 which may be the same
problem, but Greg's solution of storing HTMLs in binary won't help:
one would have to store all strings binary to fix it all right, and
that's quite bad with a more complex database...
Also, of course, one could use the binary format, but I would rather
not: thanks to XML human readability I could pin-point this problem
(which, of course, was caused by much more complex setup originally)
in a few hours; had I use the binary format and bumped into a similar
problem there, I'd have a corrupt database and no way to find what
the problem is...
Thanks for any help,
---
Ondra Čada
OCSoftware: <email_removed> http://www.ocs.cz
private <email_removed> http://www.ocs.cz/oc
DATE : Wed Jul 26 16:30:02 2006
Hello mmalc and all,
I've bumped into a CoreData bug, which self-evidently is related to
its XML generator and/or parser. Here's a simple repeat procedure:
(i) take the standard Apple example /Developer/Examples/CoreData/
EventManager
(ii) build the thing and launch
(iii) create a new event, name it
"#990000"><
(incl. quote marks), set some dates, save using XML format, close
(iv) reopen the file. The name is now '"#990000"><󱬰"><'.
Is this a known bug? More important, is there a known work-around?
Searching Cocoabuilder I've found just http://www.cocoabuilder.com/
archive/message/cocoa/2005/10/12/147940 which may be the same
problem, but Greg's solution of storing HTMLs in binary won't help:
one would have to store all strings binary to fix it all right, and
that's quite bad with a more complex database...
Also, of course, one could use the binary format, but I would rather
not: thanks to XML human readability I could pin-point this problem
(which, of course, was caused by much more complex setup originally)
in a few hours; had I use the binary format and bumped into a similar
problem there, I'd have a corrupt database and no way to find what
the problem is...
Thanks for any help,
---
Ondra Čada
OCSoftware: <email_removed> http://www.ocs.cz
private <email_removed> http://www.ocs.cz/oc
| Related mails | Author | Date |
|---|---|---|
| Ondra Cada | Jul 26, 16:30 | |
| Ondra Cada | Jul 26, 17:55 | |
| Gerriet M. Denkman… | Jul 26, 22:23 |






Cocoa mail archive

