Hugolarson

Hi, Any timeline on this feature?

Imagine a backup every minute of hundreds of databases over 5 years or more.

> Number of databases doesn't matters, as RDB$BACKUP_HISTORY is per-database. Even if one run nbackup every minute (which I highly doubt is possible on practice), then one will have 60_24_365...

I learned that the initial nbackup of initial database require switch -B 0 (level) and after that GUID is supplied instead of level. How about another exclusive switch for GUID...

Apologies, maybe I'm out of line but I need to ask if is there hope that this issue might be addressed? It would be very useful if NBACKUP can be...

> I still have no better ideas than > > * allow to `DELETE FROM RDB$BACKUP_HISTORY` if system privilege `USE_NBACKUP_UTILITY` is granted (it is how it works for `INSERT INTO...

CLEAN_HISTORY. Is it not the case that all rows beyond last N0 irrelevant? Maybe default can be delete all beyond last N0. If GUID only last nbackup is relevant?

Excellent! Are there snapshots for FB 4?

The build works and I'm testing it :) What about cleaning records without creating an actual nbackup? I think it might be useful. nbackup -CLEAN_HIST -KEEP_R 2 -U SYSDBA -P...

I miss a SimpleBigDecimalControl that can handle empty (null) values.