On 05/16/17 14:10, Ann Harrison wrote: > This is far from a simple request and would require fundamental changes to > gbak.
Taking into an account that we already have an ability NOT include data from some tables into backup/restore process I do not agree with you here :) Well - not 5 lines change but certainly very far from "fundamental changes". > Gbak is a logical dump of database contents that when restored creates a new > database. What would a restore of a partial backup create? A partial > database? Yes. > An overwritten old database? > > What benefit would this feature bring? > This can be better answered by an author of a ticket :) I can imagine for example a need to try a number of statistics queries on some predefined set of tables (including SQL debugging needs). One may try one, another, etc forms of SQL to get desired results. Later appropriate indices may be added to optimize query which provides needed result. In order not to overload production server it's good idea to work with database copy on another box. But making a copy of all TBytes of initial DB is not needed - we need a limited set of tables. In that case mentioned improvement can help making such DB backup faster (yes, it will have broken FKs, but for mentioned purporse it doesn't matter). ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
