Closed GoogleCodeExporter closed 8 years ago
The error suggests regexp failure, which sounds weird. Those have been there
for such a long time without nobody reporting errors, and I haven't seen any
problems with any mysql versions I've tried.
The regex here is '^.:[/\\]$', and by the error (missing terminating "]") it
seems like your mysql escapes the closing bracket. It shouldn't, the escape is
for the "\".
You are not using Windows, are you?
Original comment by mollify....@gmail.com
on 10 Feb 2015 at 4:43
Yes Sir, I agree, it seems to be an error of MySQL.
System is a Linux, Kernel 3.16.7-7, MySQL Server 10.0.13-MariaDB openSUSE
package
Mollify DB is an InnoDB, utf8_general_ci
Maybe there's some trouble with Kollation ? Any suggestions for further
debugging options ?
Note: with other installations of mollify no touble, same environment like this.
Original comment by soost.on...@googlemail.com
on 11 Feb 2015 at 8:48
You could try running the query directly on MySQL, for example via phpMyAdmin.
The query is this:
select id, path from item_id where path REGEXP '^.:[/\\]$'
Try to see what error is there, and can you make it work with some
modifications. For me it's hard to fix this since I don't have this error in my
system, would have to know what is wrong with that query (for me it looks
perfectly valid).
You could try something like
select id, path from item_id where path REGEXP '^.:[\/\\]$'
or
select id, path from item_id where path REGEXP '^.:[/]$'
Original comment by mollify....@gmail.com
on 11 Feb 2015 at 9:50
I tried a directly query on MySQL, and that's the result:
select id, path from item_id where path REGEXP '^.:[/]$'
This query works without an error !
So far, so good :-) How to fix it ? Shoud I do it my self in my installation ?
Tell me the place, I'll change it !
Original comment by soost.on...@googlemail.com
on 12 Feb 2015 at 12:59
So the other gave you errors? Weird, they should be all valid.
What about this one:
select id, path from item_id where path REGEXP '^.:[[.apostrophe.][.slash.]]$'
The problem is Windows, which is why I have both of the options "/" and "\"
there. I guess I could normalize Windows paths to use "/" also, that would be
the proper solution.
But the only way to change into your installation is to find/replace
recursively in all files following strings:
1) find "[/\\\\]" and replace with "[[.apostrophe.][.slash.]]" (or "[/]")
2) find "[^/\\\\]" and replace with "[^[.apostrophe.][.slash.]]" (or "[^/]")
But be careful, wrong regexp will break everything.
I'll make this accepted, as I'll try to see I could make the path normalization
and then I could remove the slash entirely from regexp.
Original comment by mollify....@gmail.com
on 12 Feb 2015 at 1:55
Yep, all other syntax of query brings error, except this one:
select id, path from item_id where path REGEXP '^.:[/]$'
Ok, I'll follow your suggestion with these steps:
1) backup the install-directory and MySQL database (it's a fresh install...)
2) find/replace recursively the query string
3) test installation again
4) reporting result
Here we go !
Original comment by soost.on...@googlemail.com
on 12 Feb 2015 at 2:58
I tried this one too (direct query):
select id, path from item_id where path REGEXP '^.:[[.apostrophe.][.slash.]]$'
MySQL Result:
#1139 - Got error 'POSIX collating elements are not supported at offset 4' from
regexp
Original comment by soost.on...@googlemail.com
on 12 Feb 2015 at 3:08
tried to search/replace the string, but this don't work properly...
Think this method isnt really a good workaround.
So I decide to stop using mollify this time and waiting for a developer
solution.
Original comment by soost.on...@googlemail.com
on 16 Feb 2015 at 9:11
[deleted comment]
I had the same error. I fixed it by replacing
[/\\\\] to [/1-\\x5C]
and
[^/\\\\] to [^/1-\\x5C]
Original comment by starose...@gmail.com
on 19 Feb 2015 at 7:13
As Google Code is announced to be shut down, I'm moving accepted issues into
GitHub: https://github.com/sjarvela/mollify/issues/12
Original comment by samuli.j...@gmail.com
on 13 Mar 2015 at 9:31
Original issue reported on code.google.com by
soost.on...@googlemail.com
on 7 Feb 2015 at 6:52