Subject | Re: [firebird-support] Bulk collate update on system tables |
---|---|
Author | Alexandre Benson Smith |
Post date | 2007-11-19T22:01:41Z |
Erick Sasse wrote:
I would not use a quick and dirty method if I have one that is safe. The
problems you will avoid is far greater than the time you will save.
If you have defined domains you only need to change in a dozen of places
and the pump process is not that slow. And you always could read your
favorite blog while the data is pumping around...
Now the problem I had encountered in my saga...
You will have some invalid data (violation of unique constraints) with
the new accent/case insensitive collation.
Let's suppose you have an Unique Constraint on People.Name, then you
have "José", "JOSÉ", "Jose" and "JOSE", all are unique in a case/accent
sensitive collation, once you change it to PT_BR you will get Unique
Constraints violations, so the data pump process will be the easiest
problem you will have to solve :-)
see you !
--
Alexandre Benson Smith
Development
THOR Software e Comercial Ltda
Santo Andre - Sao Paulo - Brazil
www.thorsoftware.com.br
> You smelled right. ;)It's easier than it looks at first sight.
> I really want to avoid creating a new db and pumping data.
>
> If I do the bulk update, backup, restore and don't get any errors, I
> should be ok, right?
>
>
I would not use a quick and dirty method if I have one that is safe. The
problems you will avoid is far greater than the time you will save.
If you have defined domains you only need to change in a dozen of places
and the pump process is not that slow. And you always could read your
favorite blog while the data is pumping around...
Now the problem I had encountered in my saga...
You will have some invalid data (violation of unique constraints) with
the new accent/case insensitive collation.
Let's suppose you have an Unique Constraint on People.Name, then you
have "José", "JOSÉ", "Jose" and "JOSE", all are unique in a case/accent
sensitive collation, once you change it to PT_BR you will get Unique
Constraints violations, so the data pump process will be the easiest
problem you will have to solve :-)
see you !
--
Alexandre Benson Smith
Development
THOR Software e Comercial Ltda
Santo Andre - Sao Paulo - Brazil
www.thorsoftware.com.br