Forum

Verify and Repair: PostgreSQL query error

Jan 05, 2015 08:40 AM

Active user

Points:: 0
Joined:: May 15, 2013

Hello,
I ran into this error while running Verify and Repair on 1C 8.3.5.1383 and PostgreSQL 9.3.4-1.1C:

Quote
EET ERROR: invalid regular expression: invalid character range

PostgreSQL query:

Code

UPDATE _Document91_VT1758 SET _Fld1761_TYPE = '\\001'::bytea, _Fld1761_S = ''::mvarchar, _Fld1761_RTRef = '\\000\\000\\000\\000'::bytea, _Fld1761_RRRef = '\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000\\000'::bytea
        WHERE (_Document91_VT1758._LineNo1759 = 1
   AND _Document91_VT1758._Fld1760RRef = '\\206q\\000\\025\\027\\015\\375\\213\\021\\337\\264\\016\\240\\211\\023\\341'::bytea
   AND _Document91_VT1758._Fld1761_TYPE = '\\010'::bytea
   AND _Document91_VT1758._Fld1761_S = ''::mvarchar
   AND _Document91_VT1758._Fld1761_RTRef = '\\000\\000\\000u'::bytea
   AND _Document91_VT1758._Fld1761_RRRef = '\\230M\\000\\014)\\236''\\374\\021\\342:3\\177\\3762:'::bytea
   AND (_Document91_VT1758._Fld11071)::mvarchar SIMILAR TO ('Prepayment: 12 944.79 EUR \\(30.00 % from 43 149.31 EUR [DOC 01AB-1234ABC]\\)'::mvarchar))
   AND _Document91_VT1758._Document91_IDRRef = '\\203V\\000\\014)\\236''\\374\\021\\342\\204\\311\\311W\\340\\217'::bytea

Problem:
A comment field in 1C (Variable string, unlimited) is incorrectly escaped in PostgreSQL:

Code
AND (_Document91_VT1758._Fld11071)::mvarchar SIMILAR TO ('Prepayment: 12 944.79 EUR \\(30.00 % from 43 149.31 EUR [DOC 01AB-1234ABC]\\)'::mvarchar))

All special characters should be fully escaped:

Code
AND (_Document91_VT1758._Fld11071)::mvarchar SIMILAR TO ('Prepayment: 12 944.79 EUR \\(30.00 \\% from 43 149.31 EUR \\[DOC 01AB-1234ABC\\]\\)'::mvarchar))

Profile

Timofey Bugaevsky	#2 Jan 13, 2015 05:19 AM
Guest Points:: Joined::	Thank you for the information, Aurimas Fišeras! I'm sorry for the late reply. We are investigating the problem.
	Profile

Timofey Bugaevsky	#3 Jan 15, 2015 04:10 AM
Guest Points:: Joined::	Hello, Aurimas Fišeras! Can you create a sample infobase which we can use to reproduce the issue? We have used the attached sample and UTF-8 collation settings for PostgreSQL. The error did not appear.
	Profile

Aurimas Fišeras

Jan 28, 2015 01:45 AM

Active user

Points:: 0
Joined:: May 15, 2013

Quote
Timofey Bugaevsky wrote: Can you create a sample infobase which we can use to reproduce the issue? We have used the attached sample and UTF-8 collation settings for PostgreSQL. The error did not appear.

Hello, Timofey Bugaevsky.

I managed to create a dt (locale: Lithuanian (Lithuania)) that exposes the problem. Just load it and run "Verify and Repair" with "Delete References" selected.

Profile

Timofey Bugaevsky	#5 Jan 30, 2015 08:21 AM
Guest Points:: Joined::	Thank you very much for your cooperation! We were able to reproduce the error, and this issue will be fixed in one of future versions of 1C:Enterprise platform.
	Profile