чт, 7 окт. 2021 г. в 11:11, Mark Rotteveel <m...@lawinegevaar.nl>:
>
> On 2021-10-06 21:27, Roman Simakov wrote:
> > ср, 6 окт. 2021 г. в 19:13, Mark Rotteveel <m...@lawinegevaar.nl>:
> >> On 06-10-2021 17:32, Roman Simakov wrote:
> >> > 9. ALTER INDEX <INDEX NAME> DROP TABLESPACE
> >> >
> >> > Data of the index will be moved to the main database.
> >>
> >> How will this work for indexes backing constraints?
> >
> > I see no problems with it. Could you explain what you mean?
>
> Sorry, I think I should have been more explicit. Is there an option to
> specify the tablespace for the constraint when defining constraints,
> instead of having to alter this after the fact (with potential issues of
> having to either find the generated index name, or making sure you name
> things explicitly).

Now it's clear. Alex mentioned that. Now there is no way but it should be added.

> >> I also think that using the old locations should be an explicit
> >> option,
> >> so if a database backup has tablespaces, and no option is specified to
> >> define the tablespace mapping, or the mapping is incomplete, restore
> >> should fail *before it started to write anything*.
> >
> > or we can restore the whole backup in the single database file without
> > tablespaces at all. I.e. merge every unmapped TS into the main
> > database.
>
> That is an interesting option as well, but I think that should be an
> explicit option as well. That is, I think trying to restore a
> tablespaced database should fail unless explicit configuration is in
> place that specifies how to handle it (restore with filenames in backup,
> explicit mapping, or 'restore into single file').

I agree. More strict rules are better in the beginning as a rule) It's
easier to add defaults later than remove them)


-- 
Roman Simakov


Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

Reply via email to