03.10.2014 10:31, Martijn Tonies wrote:
>
> I noticed that with Classic 2.5, you can get “object in use” when trying
> to modify a
> stored procedure that’s been previously executed, see also:
> http://tracker.firebirdsql.org/browse/CORE-4016
> When using “wait” on the transaction to save the proce
Thanks Dmitry.
With regards,
Martijn Tonies
Upscene Productions
http://www.upscene.com
Download Database Workbench for Oracle, MS SQL Server, Sybase SQL
Anywhere, MySQL, InterBase, NexusDB and Firebird!
03.10.2014 10:31, Martijn Tonies wrote:
>
> I noticed that with Classic 2.5, you can get
On 10/03/14 01:25, Thomas Steinmaurer wrote:
>> RELATION_NAME
>> =
>> Statement failed, SQLSTATE = 22001
>> arithmetic exception, numeric overflow, or string truncation
>> -string right truncation
>> -expected length 10, actual 21
>> SQL>
> Seems to be a problem with using the TYPE OF
Hello Claudio and all!
I found very interesting assert in backup.epp (put_data function)
fb_assert(field_count > 0 && field_count * 9 > 0 && field_count * 9 + 200 > 0)
could you explain it?
--
Roman Simakov
--
Meet P
On 02/10/2014 17:26, Thomas Steinmaurer wrote:
> Hello,
>
> I'm using the build mentioned in the subject, 32-bit, on Windows 7 64-bit.
>
> I have the following sequence of created domains in isql:
>
> SQL> create domain d_mydomain bigint;
> SQL> commit;
> SQL> create domain d_mydomain_1 bigint;
> S
On 03/10/2014 11:50, Adriano dos Santos Fernandes wrote:
> Is it required to have the others object before to make this happen?
>
> I tested with the objects you created and they're created correctly.
>
>
Also, the select query was run in ISQL or other tool?
I'm asking because some fbstuff tests s
03.10.2014 19:19, Adriano dos Santos Fernandes wrote:
> I'm asking because some fbstuff tests started failing. Some time ago,
> message buffers were cleared when the field was null, but now they seems
> to not be cleared when connected over tcp. It seems as a test problem,
> but I'm not sure how t
On 03/10/2014 12:37, Dmitry Yemanov wrote:
> 03.10.2014 19:19, Adriano dos Santos Fernandes wrote:
>
>> I'm asking because some fbstuff tests started failing. Some time ago,
>> message buffers were cleared when the field was null, but now they seems
>> to not be cleared when connected over tcp. It
03.10.2014 19:47, Adriano dos Santos Fernandes wrote:
> https://github.com/asfernandes/fbstuff/blob/master/src/test/v3api/StaticMessageTest.cpp
>
> Note the line
> "string(output->description.str,output->description.length)" for the
> SALES relation, which don't have a comment.
>
> Current (withou
On 10/03/14 15:05, Roman Simakov wrote:
> Hello Claudio and all!
>
> I found very interesting assert in backup.epp (put_data function)
>
> fb_assert(field_count > 0 && field_count * 9 > 0 && field_count * 9 + 200 > 0)
>
> could you explain it?
>
>
Looks like it's check to make sure that SSHORT doe
Hello Dmitry,
>> https://github.com/asfernandes/fbstuff/blob/master/src/test/v3api/StaticMessageTest.cpp
>>
>> Note the line
>> "string(output->description.str,output->description.length)" for the
>> SALES relation, which don't have a comment.
>>
>> Current (without a test for output->descriptionN
03.10.2014 18:21, Alex Peshkoff wrote:
> Looks like it's check to make sure that SSHORT does not overflow.
Does it really work? I thought that result of expressions like this one is
casted to
integer, so even if it overflows short, it still is bigger than zero.
--
WBR, SD.
-
03.10.2014 18:27, Martijn Tonies (Upscene Productions) wrote:
> Could the client be buggy in receiving data?
Not touching data buffer if value is null is a right thing.
--
WBR, SD.
--
Meet PCI DSS 3.0 Compliance R
Hello Dimitry,
>> Could the client be buggy in receiving data?
>
> Not touching data buffer if value is null is a right thing.
If I have a result set that simply loops over char-values, and in Delphi
get's an
empty string on NULL, that works fine.
If I have to check for "IsNull" before I ask
03.10.2014 18:41, Martijn Tonies (Upscene Productions) wrote:
> If I have a result set that simply loops over char-values, and in Delphi
> get's an
> empty string on NULL, that works fine.
>
> If I have to check for "IsNull" before I ask for the string, because I will
> get the
> -previous records
On 10/03/14 20:27, Dimitry Sibiryakov wrote:
> 03.10.2014 18:21, Alex Peshkoff wrote:
>> Looks like it's check to make sure that SSHORT does not overflow.
> Does it really work? I thought that result of expressions like this one
> is casted to
> integer, so even if it overflows short, it still
C'mon Dimitry, you cannot be serious here.
You purposefully want to break existing applications because the Firebird
client returns
the data of the previous record.
How is that useful?
With regards,
Martijn Tonies
Upscene Productions
http://www.upscene.com
Download Database Workbench for Ora
03.10.2014 21:03, Martijn Tonies (Upscene Productions) wrote:
>
> You purposefully want to break existing applications because the Firebird
> client returns the data of the previous record.
You don't get what's really happening. Firebird API (read: fbclient)
represents every field with two parts:
>> You purposefully want to break existing applications because the Firebird
>> client returns the data of the previous record.
>
>You don't get what's really happening. Firebird API (read: fbclient)
>represents every field with two parts: NULL indicator and field data.
>Ideally, nobody never shoul
03.10.2014 21:20, Martijn Tonies (Upscene Productions) wrote:
> I get exactly what's happening.
>
> And it's clear to me -something- has changed in this regard, cause if it
> weren't, everything would be just fine.
Then tell us how a properly written application (the one not ignoring
the NULL in
>> I get exactly what's happening.
>>
>> And it's clear to me -something- has changed in this regard, cause if it
>> weren't, everything would be just fine.
>
>Then tell us how a properly written application (the one not ignoring
>the NULL indicator) could be affected by this "change". Something
>w
03.10.2014 21:37, Martijn Tonies (Upscene Productions) wrote:
>
> I never said a properly written application could be affected, I said
> something
> has clearly changed as existing applications suddenly return the wrong
> result.
And I said that such existing applications are obviously buggy, but
>>> RELATION_NAME
>>> =
>>> Statement failed, SQLSTATE = 22001
>>> arithmetic exception, numeric overflow, or string truncation
>>> -string right truncation
>>> -expected length 10, actual 21
>>> SQL>
>> Seems to be a problem with using the TYPE OF clause for the data type.
>> When I re
Martijn,
> >P.S. This discussion is purely theoretical as compatibility has already
> >been restored in the meantime.
>
> I never said a properly written application could be affected, I said
> something
> has clearly changed as existing applications suddenly return the wrong result.
A change t
> 03.10.2014 21:20, Martijn Tonies (Upscene Productions) wrote:
>
>> I get exactly what's happening.
>>
>> And it's clear to me -something- has changed in this regard, cause if it
>> weren't, everything would be just fine.
>
> Then tell us how a properly written application (the one not ignoring
>
>> >P.S. This discussion is purely theoretical as compatibility has already
>> >been restored in the meantime.
>>
>> I never said a properly written application could be affected, I said
>> something
>> has clearly changed as existing applications suddenly return the wrong
>> result.
>
>A change
Martijn,
P.S. This discussion is purely theoretical as compatibility has already
been restored in the meantime.
>>>
>>> I never said a properly written application could be affected, I said
>>> something
>>> has clearly changed as existing applications suddenly return the wrong
>>> resul
P.S. This discussion is purely theoretical as compatibility has already
been restored in the meantime.
>>>
>>> I never said a properly written application could be affected, I said
>>> something
>>> has clearly changed as existing applications suddenly return the wrong
>>> result.
>>
>>
> P.S. This discussion is purely theoretical as compatibility has already
> been restored in the meantime.
I never said a properly written application could be affected, I said
something
has clearly changed as existing applications suddenly return the wrong
result.
>>> I've just checked the IBX components source, for example, and it
>>> explicitly
>>> checks
>>> for null before asking for data.
>>
>> I wonder then, Thomas, can you reproduce this issue with the IBX
>> components?
>
>Ehm, why do we care about IBX? ;-)
Cause it at least does what should be don
30 matches
Mail list logo
