Re: [Firebird-devel] gbak -r - A POX UPON ITS HOUSE

[Vlad H. <hv...@us...>]

> >>Let me put a proposal on the table for discussion:
> >>
> >>   1. We define a dpb parameter meaning "overwrite database file"
> >>   2. PIO_create be changed to fail when attempting to overwrite an
> >>      active database file always and an inactive database file in the
> >>      absense of the dpb parameter.
> >>    
> >>
> >
> >    How it differs from existing "isc_dpb_overwrite" ?
> >  
> >
> If "isc_dpb_overwrite" isn't specified, the system defaults to 
> overwriting permitted, which is backwards from want I think we want.  By 
> default, gbak doesn't specify "isc_dpb_overwrite", so it defaults to the 
> wrong behavior.

    Ah, i see it now. We must change it to false, imho
 
> Ann's proposal to change the gbak "-r" switch to the semantics of "-c" 
> strikes me as simple and elegant.  But we still need a way ask for the 
> old "-r" behavior.

    We can do the following

1. force "replace_database" switch to be typed at least with "replace"

2. add new switch "recreate_database" which can be typed with any 
    number of chars, i.e. single "r" will mean new "recreate_database"
    switch, not "replace_database". 

3. add new switch "overwrite". gbak will overwrite database only when 
    both "recreate_database" and "overwrite" used

gbak -r 
will create database and fails if it exist

gbak -replace 
or
gbak -r -overwrite
will create database and overwrite existing one



Regards,
Vlad