Thanks alot, Dimitry, I didn't know about the new (SQL spec conforming)
restirction you mentioned in your prior post!
Thomas
> Sorry, I thought that your issue was caused by the i.RDB$RELATION_NAME =
> rf.RDB$RELATION_NAME condition, but it's not. So there's only one error
> and it's explained
26.03.2013 7:42, Dmitry Yemanov wrote:
> This was an intended change which probably became an overkill. I will
> report back after closer investigation.
Sorry, I thought that your issue was caused by the i.RDB$RELATION_NAME =
rf.RDB$RELATION_NAME condition, but it's not. So there's only one erro
26.03.2013 3:33, Thomas Beckmann wrote:
> It seems to me we have a bug in nested joins:
>
> Consider the statement below. It's supposed to show foreign key fields
> which it does nicely with FB2.5. With 3.0 you'll get the error "Column
> unknown. RF.RDB$FIELD_NAME. At line 11, column 32." - this i
It seems to me we have a bug in nested joins:
Consider the statement below. It's supposed to show foreign key fields
which it does nicely with FB2.5. With 3.0 you'll get the error "Column
unknown. RF.RDB$FIELD_NAME. At line 11, column 32." - this is the
postponed on clause (i.RDB$RELATION_NAME = r
rename is done , please test for any breakings
On Mon, Mar 11, 2013 at 12:49 PM, Treeve Jelbert wrote:
> recent version of autoconf/automake/libtool complain about the firebird
> scripts
>
>
> aclocal: warning: autoconf input should be named 'configure.ac', not
> 'configure.in'
> libtoolize: put
On 03/24/13 10:22, Dmitry Yemanov wrote:
> 19.03.2013 9:54, Dmitry Kovalenko wrote:
>> Try to compile your "right way" with fourth level (/W4) compiler warnings :)
> I've committed a solution that's expected to solve both issues.
> Hopefully, it compiles on Linux :-)
>
Yes, it does. :)
--
isql under windows: different behaviour on Ctrl-BREAK depending on whether it
currently performs some job or no
---
Key: CORE-4069
URL: http://tracker.fire