*snip*
> And that's it, any suggestions other than changing the label name?
Thanks for the report and the debug output; that's very helpful.
For now, the quickest workaround will probably be to just change the
label so you can continue with your migration. I'll log this as a bug
and investigate. In theory this should work fine, but it seems like
SQLite isn't pleased with that character for some reason.
- Ryan
--
You received this message because you are subscribed to the Google Groups "larch" group.
To post to this group, send email to la...@googlegroups.com.
To unsubscribe from this group, send email to larch+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/larch?hl=en.
I'm not aware of any, since in theory Larch and SQLite should be fine
with any UTF-8 string. But this bug seems to indicate that there's
either a character encoding problem in Larch or a bug in SQLite, so
there may be more problematic characters that haven't yet been found.
- Ryan