On 26/04/17 16:34, Ann Harrison aharri...@ibphoenix.com
[firebird-support] wrote:
> If Firebird were to convert a record from its stored format through each
> intervening format, the result would be more logical but it would be a change
> to a behavior that's over 30 years old. And there are adva
> Apr 25, 2017, at 12:21 PM, Lester Caine les...@lsces.co.uk
> [firebird-support] wrote:
>
> On 25/04/17 16:50, Mark Rotteveel m...@lawinegevaar.nl
> [firebird-support] wrote:
>> The SQL standard is quite clear at what needs to happen: adding a new
>> column with a default should behave as if
On 25-4-2017 18:21, Lester Caine les...@lsces.co.uk [firebird-support]
wrote:
> On 25/04/17 16:50, Mark Rotteveel m...@lawinegevaar.nl
> [firebird-support] wrote:
>> The SQL standard is quite clear at what needs to happen: adding a new
>> column with a default should behave as if that column has e
2017-04-25 11:24 GMT-03:00 Svein Erling Tysvær setys...@gmail.com
[firebird-support] :
>
>
> Hi everyone,
>>
>> I encountered strange behavior droping a column definition with default
>> value.
>>
>> The environment is Ubuntu 16.04 LTS 64 bits, Firebird version
>> LI-V2.5.6.27020 (Firebird 2.5 Sup
On 25/04/17 16:50, Mark Rotteveel m...@lawinegevaar.nl
[firebird-support] wrote:
> The SQL standard is quite clear at what needs to happen: adding a new
> column with a default should behave as if that column has existed from
> the original create table (btw: irrespective of the NOT NULL constrai
On 25-4-2017 17:43, Lester Caine les...@lsces.co.uk [firebird-support]
wrote:
> On 25/04/17 12:51, Maxi maxiroba...@gmail.com [firebird-support] wrote:
>> I expect the value assigned by DEFAULT when I add the new field is
>> still there.
>
> There has been various discussions on this area ...
>
>
On 25/04/17 12:51, Maxi maxiroba...@gmail.com [firebird-support] wrote:
> I expect the value assigned by DEFAULT when I add the new field is
> still there.
There has been various discussions on this area ...
If you add 'NOT NULL' to an existing field, then you need to populate
the existing field
On 24-4-2017 20:50, Maxi maxiroba...@gmail.com [firebird-support] wrote:
>
>
> Hi everyone,
>
> I encountered strange behavior droping a column definition with default
> value.
>
> The environment is Ubuntu 16.04 LTS 64 bits, Firebird version
> LI-V2.5.6.27020 (Firebird 2.5 SuperClassic)
>
>
> I'll
>
> Hi everyone,
>
> I encountered strange behavior droping a column definition with default
> value.
>
> The environment is Ubuntu 16.04 LTS 64 bits, Firebird version
> LI-V2.5.6.27020 (Firebird 2.5 SuperClassic)
>
>
> I'll try to explain with an example. The statement sequence is:
>
> 1. Create t
2017-04-24 16:39 GMT-03:00 'Leyne, Sean' s...@broadviewsoftware.com
[firebird-support] :
>
>
>
>
> > 3. Alter the table
> > ALTER TABLE "SCHEMA_AUTHOR" ADD "SURNAME" varchar(15) DEFAULT
> > 'surname default' NOT NULL
> >
> > After step 3, I have a record with a new column with 'surname default'
>
> 3. Alter the table
> ALTER TABLE "SCHEMA_AUTHOR" ADD "SURNAME" varchar(15) DEFAULT
> 'surname default' NOT NULL
>
> After step 3, I have a record with a new column with 'surname default' value
> into SURNAME field.
>
> 4. Drop default definition
> ALTER TABLE "SCHEMA_AUTHOR" ALTER COLUMN "SUR
Hi everyone,
I encountered strange behavior droping a column definition with default
value.
The environment is Ubuntu 16.04 LTS 64 bits, Firebird version
LI-V2.5.6.27020 (Firebird 2.5 SuperClassic)
I'll try to explain with an example. The statement sequence is:
1. Create the table
CREATE TABLE
12 matches
Mail list logo
