[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kexi
Subject:    Re: [Kexi] LIMIT 1 in Select Clause
From:       Sharan Rao <sharanrao () gmail ! com>
Date:       2007-12-12 21:49:30
Message-ID: 200712130356.35624.sharanrao () gmail ! com
[Download RAW message or body]

On Tuesday 04 Dec 2007 7:17:42 pm Jarosław Staniek wrote:
> Sharan Rao said the following, On 2007-12-01 21:17:
> >  I was facing problems with the function Connection::querySingleString()
> > in Sybase, as the " LIMIT " clause is not supported.
>

Hmm, new thing I noticed in the Limit 1 clause. ( I should have noticed it 
before, but I tested the clause only in commandline tsql , and not Kexi, 
before committing :( ),

Sybase gives a warning ( in Sybase Central ) if I execute a query of the type
 "Select Top 1 fooColumn from fooTable where fooClause"

Warning: "The result returned is non-deterministic"
Of course, that's because there's no specific ordering specified. Now, 
unfortunately, this is returned as an error in freetds/dblib !!

Now, we do have a columnNumber being passed to Connection::querySingleString() 
as a param, but would an "Order by " clause on that column be right in the
case if there are multiple rows ? I guess querySingleString() is not intended 
to be used where multiple row/multiple column results are returned :) ( as 
the documentation suggests )

Any hints ?

Cheers!
 Sharan Rao







_______________________________________________
Kexi mailing list
Kexi@kde.org
https://mail.kde.org/mailman/listinfo/kexi

[prev in list] [next in list] [prev in thread] [next in thread]