|Subject||Re: Things to consider?|
>>It always intriged me how MSSQL, Sysbase, Watcom, etc had a single
setting to determine case-insensitivity across the entire DB.
Whilst looking in this tonight I created a blank DB in MSSQL and
it turns out that it uses a default setting from the registry:
is 'Latin1_General_CI_AS' and this is *case-insensitive* by default.
--- In Firebird-Architect@yahoogroups.com, "Arno Brinkman"
> > Perhaps a database administration tool could fix this "issue"?
> > you set the default collation in it, and it add collation to each newtools that
> > column automatically. Of course, you would have to use admin.
> > have such feature.the default
> This can already be done by setting the RDB$DEFAULT_COLUMN_NAME from
> RDB$CHARACTER_SET_NAME. Though you must keep in mind that thisdefault value doesn't survive a
> backup/restore!Do we have Latin1_General_CI_AS (or an equivalent?)
> Arno Brinkman