I don't know if this is possible but, I was going to add Barry's justification functions into my database and realised I have to change the collation. I think most people are simply going to use whatever their default collation is.

Would it be possible to have a default collation defined for the database and then simply use that?

This would make things more portable (functions, procedures, table definitions?)

Roy Lambert

Roy,

> Would it be possible to have a default collation defined for the database and then simply use that?

Do you mean this:

EDBManager
File | Preferences | Dialogs

?

Uli

Uli


>> Would it be possible to have a default collation defined for the database and then simply use that?
>
>Do you mean this:
>
>EDBManager
>File | Preferences | Dialogs

Good try but no

From Barry's post

CREATE FUNCTION "LeftJustify" (IN "aValue" VARCHAR COLLATE UNI_CI, IN "aWidth" INTEGER, IN "aFillChar" CHAR(1) COLLATE UNI_CI)

What I'd like is

CREATE FUNCTION "LeftJustify" (IN "aValue" VARCHAR, IN "aWidth" INTEGER, IN "aFillChar" CHAR(1))

Its trivial for me to alter the UNI_CI to ANSI_CI on each individual occasion, and its forced when I try and install in my non-unicode EDBManager but if a (to me) weird collation was used that did exist it could have "interesting" consequences - what I'm not sure but that's part of the problem.

Roy

Roy,

Ok I misinterpreted that.

Uli

Roy,

<< Would it be possible to have a default collation defined for the database
and then simply use that? >>

Yes.  It's actually already in the database catalog and Databases system
table, but not implemented in the CREATE/ALTER DATABASE statement yet.

BTW, you can leave off the COLLATE clause now, it's just that the collation
will default to ANSI or UNI, depending upon the version being used.

Tim Young
Elevate Software
www.elevatesoft.com