On 2018-06-21 10:34, André Knappstein Knappstein@...
[firebird-support] wrote:

> If it is what I think it is then it is probably widely known, just not
> to me :-)
>
> I would like to get certain, though, because I do have some respect
> for things happening and looking strange (might always be an early
> sign of some corrution) so here goes:
>
> Do new columns - without having inserted anything to them and without
> any default value nor being part of any constraint - not make it into
> the next backup?
>
> I have the - for me - strange situation that I added 2 columns to a
> production database, left them completely NULLed, created backup,
> restored to local backup-database;
> the local backup then contained all the latest records of the tables
> in question, but not the new columns.
>
> I tried several times, no changes, then I added a single value in each
> of the columns and they got restored to the local test database.
>
> Thanks in advance for confirmations/warnings!

I would first rule out the possibility that the change was not
committed. Both DDL and gbak are transactional, so not having committed
the table change would result in that change not being part of the gbak
backup.

Otherwise, it would be really helpful to have a full reproduction
recipe, including all relevant version information.

Mark