Hello, All.
What's the purpose for following code in subj?
> InternalMessageBuffer inMsg(m_inMetadata, m_in_buffer.begin());
> InternalMessageBuffer outMsg(m_outMetadata, m_out_buffer.begin());
>
> m_request->execute(&status, transaction,
> inMsg.metadata, in
> What's the purpose for following code in subj?
If you really interested, you can look at few previous revisions of this
code.
>> InternalMessageBuffer inMsg(m_inMetadata, m_in_buffer.begin());
>> InternalMessageBuffer outMsg(m_outMetadata, m_out_buffer.begin());
>>
>> m_request->execute
08.03.2014 14:18, Vlad Khorsun wrote:
> If you really interested, you can look at few previous revisions of this
> code.
From code changes and commit comments it looks like Alex just did some mass
search-and-replace cleanup without real cleaning of pointless code.
> With current sta
group by from derived table which contains group by on field with LITERAL value
returns wrong result
Key: CORE-4360
URL: http://tracker.firebirdsql.org/browse/COR
It seems today is not my day.
I was playing to put more security on system tables, but I ran on a series
of bugs. At this time I'm not really sure if it's just me, so I need others
to comment.
SQL> insert into rdb$database values(null,null,null,null,null);
Statement failed, SQLSTATE = 28000
no pe
09.03.2014 12:00, Claudio Valderrama C. wrote:
>
> Ok, as I said, this restriction already exists, but the message is not good.
> Unlike Ann, I'm not a debugging wizard, but because I couldn't make sense of
> it by reading the sources, I had to call VS and found that an ACL is corrupt
> when walk_a
