Part of gbak messages from services is lost before error message
-----------------------------------------------------------------

                 Key: CORE-3429
                 URL: http://tracker.firebirdsql.org/browse/CORE-3429
             Project: Firebird Core
          Issue Type: Bug
          Components: GBAK
    Affects Versions: 2.5.0
         Environment: FB 2.5, Windows 2003SP1
            Reporter: Yurij
            Priority: Minor


When restoring invalid backup(e.g. with nulls in not null column) through 
services API and with -v option, part of informational log messages just before 
an error message is lost. 
With error message not containing table name, it becomes difficult to determine 
which table caused an error.

When restoring without services API, all informational messages appears in log:

with services API:
gbak:restoring data for table ROUTES
gbak:   8 records restored
gbak:    restoring index PK_ITINTAGS
..... here about 20 messages is lost...
gbak: ERROR:validation error for column EVT_NULLBUG, value "*** null ***"
gbak: ERROR:    warning -- record could not be restored

without services API:
gbak:    restoring index U_SEN_ID
gbak:    restoring index PK_EVT_ID
gbak:    restoring index IDX_EVT_DT
gbak:restoring data for table EVENTS
gbak: ERROR:validation error for column EVT_NULLBUG, value "*** null ***"
gbak: ERROR:warning -- record could not be restored


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

        

------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

Reply via email to