Regex bug with initial optional parentheses
Bug #1026055 reported by
Amir Zeldes
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ANNIS |
Triaged
|
Critical
|
Thomas Krause |
Bug Description
When using Regex matches, an optional parentheses is ignored. For example:
pos=/(APPR)?ART/
only finds pos="ART", but not pos="APPR"
The following query works fine:
pos=/^(APPR)?ART/
Changed in annis: | |
status: | New → Confirmed |
milestone: | none → 3.0.0 |
status: | Confirmed → Triaged |
To post a comment you must log in.
Seems like the bug Viktor found in PostgreSQL itself: http:// archives. postgresql. org/message- id/201207061849 51.GA91000% 40client195- 161.wlan. hu-berlin. de
This was fixed in PostgreSQL itself (http:// git.postgresql. org/gitweb/ ?p=postgresql. git;a=commit; h=628cbb50ba80c 83917b07a7609dd ec12cda172d0) and will be backported to 8.4 (http:// git.postgresql. org/gitweb/ ?p=postgresql. git;a=commit; h=b9edaa784e407 d1b6e890b776c60 7a26f3aa7e49) and 9.1 (http:// git.postgresql. org/gitweb/ ?p=postgresql. git;a=commit; h=a9287de176045 0e7fe3b4309ee1b a7ea2af39217)
We should wait for the official releases and if this fixes the problem make a public anouncement to upgrade.