Restore of IB XE3 backup containing a domain based on BOOLEAN fails
-------------------------------------------------------------------

                 Key: CORE-5820
                 URL: http://tracker.firebirdsql.org/browse/CORE-5820
             Project: Firebird Core
          Issue Type: Bug
    Affects Versions: 4.0 Alpha 1
         Environment: Windows 7
            Reporter: Bert Herngreen


I'm aware that the differences between IB and Firebird will get bigger and 
bigger, however could the following be fixed?

An Interbase XE3 backup (in transportable format) of a database holding a 
table, which uses a domain based on the BOOLEAN datatype can't be restored 
fully:

CREATE DOMAIN DMN_BOOLEAN AS BOOLEAN

CREATE TABLE FAILURE (
  BOOL_FIELD       DMN_BOOLEAN
);

This specific table won't be restored resulting in an error message:

gbak:committing metadata for table FAILURE 
gbak:error committing metadata for table FAILURE 
gbak: ERROR:unsuccessful metadata update 
gbak: ERROR:    FAILURE 

Also afterwards connecting to the database and calling the create table 
statement by hand will result in the same errror.

However when a new domain in the same (partly) restored DB is created:

CREATE DOMAIN DMN_BOOLEAN2 AS BOOLEAN

CREATE TABLE SUCCESS (
  BOOL_FIELD       DMN_BOOLEAN2
);

This succeeds.
The problem only seems to appear in the case of restoring domains based on 
BOOLEAN datatypes as a domain of INTEGER type succeeds.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
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

Reply via email to