Hi,
Will be good to have some configurable option for data type result for count(*).
In FB3 result rype is bigint in previous it was integer.
All projects which use integer in designer faill becouse of that.
Regards,
Karol Bieniaszewski
On Tue, 03 Dec 2013 12:10:30 +0100, liviusliv...@poczta.onet.pl
liviusliv...@poczta.onet.pl wrote:
Hi,
Will be good to have some configurable option for data type result for
count(*).
In FB3 result rype is bigint in previous it was integer.
All projects which use integer in designer
03.12.2013 15:10, liviusliv...@poczta.onet.pl wrote:
All projects which use integer in designer faill becouse of that.
I'm wondering what connectivity layer do you refer to and what error it
raises. I don't see why it should fail provided that the returned value
does not overflow the 2^32
On 12/3/2013 6:24 AM, Mark Rotteveel wrote:
On Tue, 03 Dec 2013 12:10:30 +0100, liviusliv...@poczta.onet.pl
liviusliv...@poczta.onet.pl wrote:
Hi,
Will be good to have some configurable option for data type result for
count(*).
In FB3 result rype is bigint in previous it was integer.
All
03.12.2013 16:59, Jim Starkey wrote:
Another possibility is to be smarter about upgrades. For example,
counts could be int64s and exceptions thrown if an assignment results in
loss of data. This would let earlier applications continue to work
while still allowing applications to count 2G to
03.12.2013 21:09, Dimitry Sibiryakov wrote:
It won't help. If in Delphi db-aware components fields were created in design
time and
this field was created with type ftInteger, there is no way FB API can find
it out and
report ISC_LONG instead of ISC_INT64.
Doesn't it mean that such an
03.12.2013 18:25, Dmitry Yemanov wrote:
Doesn't it mean that such an application will be always passing SQL_LONG
to execute/fetch calls?
No, it is much more stupid. Application get ISC_INT64 from API, derive
fields type
fbBigint from it, compare it with already configured ftInteger, feel
On 12/3/2013 12:31 PM, Dimitry Sibiryakov wrote:
03.12.2013 18:25, Dmitry Yemanov wrote:
Doesn't it mean that such an application will be always passing SQL_LONG
to execute/fetch calls?
No, it is much more stupid. Application get ISC_INT64 from API, derive
fields type
fbBigint from it,
