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
Comments
Commented by: Alice F. Bird (firebirds) Date: 2005-07-24 21:44 Dmitry, The problem is not that DEFAULT_COLLATE_NAME is not The real problem is that all character sets and collations I'd reported the same thing to Claudio two days ago about Maybe we should treat RDB$CHARACTER_SETS and RDB$COLLATIONS What do you think? |
Commented by: Alice F. Bird (firebirds) Date: 2005-07-24 18:26 Adriano, do you agree? Could you please take care about this? |
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 - restore the same backup created (witout problems) in 2.0 I get the following error: Regards |
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 |
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 |
Modified by: @pcisarWorkflow: jira [ 10813 ] => Firebird [ 15238 ] |
Modified by: @asfernandesstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.5 Alpha 1 [ 10224 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovQA Status: No test |
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
The text was updated successfully, but these errors were encountered: