Zeoslib Portal

Well, that's not all. That patch only works for procedures returning single value or set of values.

To make this all work more patches are required. There are few problems with procedures returning record types etc.

EgonHugeist , Ok. Then I'll just leave this patch with my FetchOutParams implementation for TZPostgreSQLCallableStatement here. I used ResultSet to retrieve values of the first row from output. But to make it work I had to remove rtForwardOnly check in TZPostgreSQLResultSet.MoveAbsolute, because it...

EgonHugeist,

I found a one more place, where you might also want to use SetStatementParam:
TZUpdateSQL.FillStatement

EgonHugeist , Still testing, but seems to work fine. And what about TZPostgreSQLConnection.GetEscapeString? A query like q.SQL.Text := 'select * from sys_values where sysval_name = :sn'; q.ParamByName('sn').AsString := 'QMenu\QUICKMENUROWCOUNT'; And I get final query like select * from sys_values w...

EgonHugeist , How about reverting to old MySQL implementaion just for PG? {** Return a quoted string token from a reader. This method will collect characters until it sees a match to the character that the tokenizer used to switch to this state. @return a quoted string token from a reader } functio...

EgonHugeist,

checked rev.1576. Tried it with testcase
select '\\' || :str

and got

One more thing. Seems like TZPostgreSQLConnection.GetEscapeString does exactly opposite to what I described about standard_conforming_strings.

When ON - it encodes it, but it shouldn't.

Ok, I'll check it.
By the way, found a little bug.

EgonHugeist , I didn't actually get your question about fullunicode IDEs. If you are talking about Preprepare property - it's probably not needed in there, because Strings are always unicode. So you always have to cast/encode it to ClientEncoding without escaping. Such strings can even be mixed wit...

Can't find that thread. Was it dropped for good? )

One more thing:
valid quote escape syntax is ''(two quotes), but depending on
backslash_quote parameter, it is possible to use \' to escape quote

Well, it's not that easy as I thought. Many things in tokenizing PostreSQL strings depend on standard_conforming_strings parameter. So I'll have to give samples for both cases. standard_conforming_strings=on In this case backslashes are treated just as they are: '\\' is treated as \\ '\n' = \n '\' =...

Yes, everything's fine.
Thank you!

EgonHugeist , didn't want to confuse you. Postgre tokenizer uses inherited (MySql) tokenizer. Look at this part of TZMySQLQuoteState.NextToken end; end; end else if (ReadChar = BackSlash) and (TempLastChar = BackSlash) then Result.TokenType := ttEscapedQuoted end else if ReadChar = BackSlash then T...

I guess error is in TZMySQLQuoteState.NextToken