Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Collation backup of RDB$DEFAULT_COLLATE_ [CORE789] #1173

Closed
firebird-issue-importer opened this issue Sep 17, 2003 · 10 comments
Closed

Collation backup of RDB$DEFAULT_COLLATE_ [CORE789] #1173

firebird-issue-importer opened this issue Sep 17, 2003 · 10 comments

Comments

@firebird-issue-importer

Submitted by: @pcisar

SFID: 807996#⁠
Submitted By: pcisar

It would be very nice if
RDB$DEFAULT_COLLATE_NAME in table
RDB$CHARACTER_SETS works with backup and
restore.

When i change the default collate like :

update RDB$CHARACTER_SETS
set RDB$DEFAULT_COLLATE_NAME = 'DU_NL'
where RDB$CHARACTER_SET_NAME = 'ISO8859_1'

Every new created (var)Char automaticly has the default
characterset / collate.

Currently when an Backup / Restore is done these
information is lost.

Regards,
Arno

Commits: 28bf8b4

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jun 14, 2006

Commented by: Alice F. Bird (firebirds)

Date: 2005-07-24 21:44
Sender: asfernandes
Logged In: YES
user_id=940451

Dmitry,

The problem is not that DEFAULT_COLLATE_NAME is not
backed-up. It is.

The real problem is that all character sets and collations
initialized by the engine has RDB$SYSTEM_FLAG = 1.

I'd reported the same thing to Claudio two days ago about
COMMENT ON and RDB$DESCRIPTION.

Maybe we should treat RDB$CHARACTER_SETS and RDB$COLLATIONS
specially, backing-up system items and modifing records in
restore.

What do you think?

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jun 14, 2006

Commented by: Alice F. Bird (firebirds)

Date: 2005-07-24 18:26
Sender: dimitr
Logged In: YES
user_id=61270

Adriano, do you agree? Could you please take care about this?

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jun 16, 2006

Modified by: @pcisar

issuetype: New Feature [ 2 ] => Improvement [ 4 ]

SF_ID: 807996 =>

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Apr 22, 2007

Commented by: Poul Dige (tabulex)

I don't know if this is related, but when I try t

to backup a 2.0 database in 2.1
**********
gbak: writing domain RDB$287
gbak: writing domain RDB$288
gbak: writing domain RDB$289
gbak:writing shadow files
gbak:writing character sets
gbak:writing collations
gbak:writing tables
gbak: ERROR:Unable to complete network request to host "127.0.0.1".
gbak: ERROR: Error reading data from the connection.
gbak: ERROR: An existing connection was forcibly closed by the remote host.
gbak:Exiting before completion due to errors
**********

- restore the same backup created (witout problems) in 2.0 I get the following error:
**********
gbak: committing metadata
gbak: ERROR:unsuccessful metadata update
gbak: ERROR: TANSAETTELSE <- one of the tables in the db
gbak: ERROR: CHARACTER SET ISO8859_1 is not installed
gbak:Exiting before completion due to errors
**********
At some point I got a collation error, "ISO8859_1 not installed" during the restore process, but I can'r reproduce it right now...

Regards
Poul Dige
Tabulex

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Apr 22, 2007

Commented by: Poul Dige (tabulex)

Doh!

The 8859_1-bug that I mentioned above IS actually a part of the problem that GBAK reports during restore... so it is quite easy to reproduce :)

Poul

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Apr 22, 2007

Commented by: Poul Dige (tabulex)

Sorry!

Above seems to origin from uninstalling FB2.0 and installing FB2.1 still having a 2.0 process running (CS). after killing all FB-related processes in the taskmanager and restarting FB2.1 everything seems to work (at least for now :)

Regards
Poul

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jan 28, 2008

Modified by: @pcisar

Workflow: jira [ 10813 ] => Firebird [ 15238 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Apr 11, 2008

Modified by: @asfernandes

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.5 Alpha 1 [ 10224 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Nov 12, 2009

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jan 19, 2016

Modified by: @pavel-zotov

QA Status: No test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants