28.11.2014 00:15, Mark Rotteveel wrote:
> Interesting, I assume that is for dialect 1 as it doesn't have quoting?
Supposedly, yes. This trick was inherited from InterBase and we try to
maintain it (when it's not forgotten :-).
> Sounds like a plan :)
>
> I will address the keyword_or_column and
On 27-11-2014 17:12, Dmitry Yemanov wrote:
> 26.11.2014 18:52, Mark Rotteveel wrote:
>> What do you want me to do?
>
> Keep your current solution.
>
>>> 3) New reserved words (OFFSET and ROW) should be added to the
>>> keyword_or_column rule to simplify migration. That said, I'm wondering
>>> why R
26.11.2014 18:52, Mark Rotteveel wrote:
>
> I initially had a similar implementation (slightly more complex), but I
> decided to extend select_expr so the new production reads more like the
> production in the SQL standard:
>
> Compare parse.y:
> select_expr
> : ...
> | with_clause sele
2014-11-27 12:47 GMT+04:00 Dimitry Sibiryakov :
> 27.11.2014 9:40, Alexpux wrote:
> > I’m already build debug version of firebird.
> > I'm set breakpoint on is_attach_database (why.cpp:1361) but it not go
> there - it just segfault on calling is_attach_database without going to
> this proc. So I t
27.11.2014 9:40, Alexpux wrote:
> I’m already build debug version of firebird.
> I'm set breakpoint on is_attach_database (why.cpp:1361) but it not go there -
> it just segfault on calling is_attach_database without going to this proc. So
> I think this is can be calling convention issue.
Dis
> 26 нояб. 2014 г., в 22:32, Dimitry Sibiryakov написал(а):
>
> 26.11.2014 20:01, Alexpux wrote:
>
>> We think this maybe the issue for 64-bit as 64-bit don’t use stdcall
>> convention.
>
> It doesn't matter, calling convention attribute is silently (or with
> warning) ignored
> on 64 bit
