Almost all the error messages of Firebird are insuficient, don't give
enough information, they would be very more useful when in all cases naming
the table and the column that have the error.
For example, the message "data truncated" never says which is the column
with that error, and if the table
On 25/10/2013 13:50, Vlad Khorsun wrote:
BTW: Would it be possible to include the name of the actual constraint
that was violated?
>>> CREATE TABE T
>>> (
>>> F1 INT NOT NULL,
>>> F2 INT CHECK(F2 >= 0)
>>> )
>>>
>>> what constraint name would you like to report in both cases ? :)
>> D
25.10.2013 17:43, Vlad Khorsun wrote:
> what if expression is very long and multyline ?
In this case DB developer will give it a meaningful name.
> Also, it will force engine
> to make query system table to obtain constraint source...
Throwing constraint violation exception is not fre
>>> BTW: Would it be possible to include the name of the actual constraint
>>> that was violated?
>>
>> CREATE TABE T
>> (
>> F1 INT NOT NULL,
>> F2 INT CHECK(F2 >= 0)
>> )
>>
>> what constraint name would you like to report in both cases ? :)
>
> Doesn't that get assigned an internal name (
>>> BTW: Would it be possible to include the name of the actual constraint
>>> that was violated?
>>
>> CREATE TABE T
>> (
>> F1 INT NOT NULL,
>> F2 INT CHECK(F2 >= 0)
>> )
>>
>> what constraint name would you like to report in both cases ? :)
>>
>> Regards,
>> Vlad
>>
>
> In the first case
On Fri, 25 Oct 2013 17:58:08 +0300, "Vlad Khorsun"
wrote:
>> I agree, the current message is even nonsensical, because the insert
(or
>> update) did not fail because the column definition includes validation
>> constraints, but because the insert violated one of those constraints.
>>
>> BTW: Woul
El 25/10/2013, a las 16:58, "Vlad Khorsun"
escribió:
>> On Fri, 25 Oct 2013 16:31:56 +0200, Dimitry Sibiryakov
>> wrote:
>>> 25.10.2013 16:17, Vlad Khorsun wrote:
Also, i consider accompanied SQL CODE message
The insert failed because a column definition includes
>>>
> On Fri, 25 Oct 2013 16:31:56 +0200, Dimitry Sibiryakov
> wrote:
>> 25.10.2013 16:17, Vlad Khorsun wrote:
>>> Also, i consider accompanied SQL CODE message
>>>
>>> The insert failed because a column definition includes
>>> validation constraints.
>>>
>>> is not good, as it
On Fri, 25 Oct 2013 16:31:56 +0200, Dimitry Sibiryakov
wrote:
> 25.10.2013 16:17, Vlad Khorsun wrote:
>> Also, i consider accompanied SQL CODE message
>>
>> The insert failed because a column definition includes
>> validation constraints.
>>
>> is not good, as it is the same
25.10.2013 16:17, Vlad Khorsun wrote:
> Also, i consider accompanied SQL CODE message
>
> The insert failed because a column definition includes validation
> constraints.
>
> is not good, as it is the same for both INSERT and UPDATE statements.
> I offer to change it by something lik
> Specify the name of the table, if an exception occurs when insert
> -
>
> Key: CORE-4252
> URL: http://tracker.firebirdsql.org/browse/CORE-4252
> Project: Firebird Core
> Issue Typ
UDF Declaration localname and entrypoint
Key: CORE-4253
URL: http://tracker.firebirdsql.org/browse/CORE-4253
Project: Firebird Core
Issue Type: Bug
Components: UDF
Environment: Wind
12 matches
Mail list logo
