Thanks everyone!
The problem has been solved, and the odd characters are gone.
The query didn't work without some modifications. I ended up using
select xwd_fullname from xwikidoc where xwd_content like '%' || chr(1) ||
'%';
(concat() only takes two operands, so it was easier to use ||. My sqlp
Hello all,
here would be the query:
select xwd_fullname from xwikidoc where xwd_content like
concat("%",char(1),"%");
(I've seen many indicate that || would be the concatenation operator,
but it seems like it is not the case in like operands)
Based on that, Peter, you should be able to filter t
What I can say from the error is that the character is in a document
content at least (not a title, or an object) but it does not help much
reduce the scope.
You could try to find it with a SQL request I guess, need to find how
to search this specific character in a SQL request.
On Mon, Feb 22, 2
Hi Peter,
On 22 Feb 2016 at 12:46:33, Peter John Acklam
(pjack...@gmail.com(mailto:pjack...@gmail.com)) wrote:
> Avoiding this problem in the future would be nice, but I already have this
> character in my wiki, and I need to get rid of it. I don't know how it got
> there, but more importantly,
On Mon, Feb 22, 2016 at 12:46 PM, Peter John Acklam wrote:
> Avoiding this problem in the future would be nice, but I already have this
> character in my wiki, and I need to get rid of it. I don't know how it got
> there, but more importantly, I need to find it, so I can remove it. With no
> XAR e
Avoiding this problem in the future would be nice, but I already have this
character in my wiki, and I need to get rid of it. I don't know how it got
there, but more importantly, I need to find it, so I can remove it. With no
XAR export, we can't do our planned transision from an Oracle to a
Postgr
Starting a discussion on this subject on
http://markmail.org/message/32vnzxchphr26phh.
If you have more input on what is this character doing here please share there.
On Mon, Feb 22, 2016 at 11:55 AM, Thomas Mortagne
wrote:
> Actually I do know why it's writting XML 1.0, that's because we tell i
Actually I do know why it's writting XML 1.0, that's because we tell it to...
Did not know XML 1.0 was not supporting anything, I'm surprise we get
this kind of report only know.
Anyway thanks for the report, will take care of this.
On Mon, Feb 22, 2016 at 11:31 AM, Thomas Mortagne
wrote:
> Wha
What I understand from the error message is that Woodstox think it's
writing XML 1.0 and looks like it's not possible to put anything you
want in XML 1.0 but not sure why exactly. You happen to have a
document containing some weird character (0x1) which is probably a
mistake but still we should be
I can no longer make a XAR export of our wiki. The essential error message
in catalina.out seems to be
"Invalid white space character (0x1) in text to output (in xml 1.1, could
output as a character entity)"
Alas, there is no information about which wiki page contains this invalid
character. I ca
10 matches
Mail list logo
