10.08.2013 21:20, liviuslivius пишет:
>
> and i test this also against Oracle 11g
> and try SELECT T.ID, row_Number() over() FROM TEST
> i get error the same as in MSSQL
> "Error: ORA-30485: missing ORDER BY expression in the window specification"
PGSQL 9.1:
postgres=# select id from test;
id
-
W dniu 2013-08-10 09:39:43 użytkownik Mark Rotteveel
napisał:
> On 10-8-2013 09:08, liviuslivius wrote:
> > Hi,
> >
> > you do not understand me correctly
> > i talking about query with over() not over(order by)
> > i know that i can specify many row_number clause in one query
> >
> > Firebird
On 10-8-2013 15:15, Dmitry Yemanov wrote:
>>> It executes:
>>> "SELECT RDB$DB_KEY,"ID","LONG_STR","STR","CamelStr"
>>> FROM TEST_TABLE2 WHERE
>>> RDB$DB_KEY = ?"
>>>
>>> Where the parameter is set to:
>>> sqltype = 453
>>> sqlscale = 0
>>> sqlsubtype = 1
>>> sqllen = 8
>>> sqldata = { 0x81, 0, 0,
On 10-8-2013 15:03, Dmitry Yemanov wrote:
> 10.08.2013 16:15, Mark Rotteveel wrote:
>>
>> I am still wondering though if it shouldn't actually be using xdr_bool
>> instead of xdr_opaque.
>
> For byte streams (and CHAR[1] can be surely considered a byte stream)
> xdr_opaque is a correct choice. BTW,
10.08.2013 12:20, Mark Rotteveel wrote:
>
>> Has anything changed in Firebird 3.0 with the stability of RDB$DB_KEY or
>> how RDB$DB_KEY works?
Nothing, AFAIR (for the regular tables).
>> It executes:
>> "SELECT RDB$DB_KEY,"ID","LONG_STR","STR","CamelStr"
>> FROM TEST_TABLE2 WHERE
>> RDB$DB_KEY =
10.08.2013 16:15, Mark Rotteveel wrote:
>
> I am still wondering though if it shouldn't actually be using xdr_bool
> instead of xdr_opaque.
For byte streams (and CHAR[1] can be surely considered a byte stream)
xdr_opaque is a correct choice. BTW, I failed to find xdr_bool in trunk,
perhars it wa
On 10-8-2013 08:36, Mark Rotteveel wrote:
> Anyone?
>
> On 8-8-2013 19:10, Mark Rotteveel wrote:
>> I was looking at implementing boolean in Jaybird trunk (+ backport to
>> 2.2.x), but I'd like some confirmation on how it is encoded in the
>> XSQLVAR and in the wireprotocol.
>>
>> A quick skim of t
On 4-8-2013 14:39, Mark Rotteveel wrote:
> Has anything changed in Firebird 3.0 with the stability of RDB$DB_KEY or
> how RDB$DB_KEY works?
>
> Jaybird uses RDB$DB_KEY to refresh (and update) rows in updatable
> ResultSets, one of the tests now fails because it cannot find the row it
> wants to ref
On 10-8-2013 09:08, liviuslivius wrote:
> Hi,
>
> you do not understand me correctly
> i talking about query with over() not over(order by)
> i know that i can specify many row_number clause in one query
>
> Firebird allow this construction over(without order by) and then it should
> numerate reco
Hi,
you do not understand me correctly
i talking about query with over() not over(order by)
i know that i can specify many row_number clause in one query
Firebird allow this construction over(without order by) and then it should
numerate records in resultset sequential
Example MSSQL disallow ro
10 matches
Mail list logo
