Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 4 of 4 total
Thread Charcase
Sat, Dec 16 2006 11:37 AMPermanent Link

Fernando Dias

Team Elevate Team Elevate

Tim,

Is there something equivalent to CHARCASE in EDB ?

--
Fernando Dias

Sat, Dec 16 2006 5:26 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Fernando,

<< Is there something equivalent to CHARCASE in EDB ? >>

No.  If you want a column to be upper-cased, then you'll have to write a
trigger to do it.

--
Tim Young
Elevate Software
www.elevatesoft.com

Sat, Dec 16 2006 6:01 PMPermanent Link

"Johnnie Norsworthy"
"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:9F7BF79A-DD19-43EB-BDA3-D6EE230E62FA@news.elevatesoft.com...
> Fernando,
>
> << Is there something equivalent to CHARCASE in EDB ? >>
>
> No.  If you want a column to be upper-cased, then you'll have to write a
> trigger to do it.

Does this basically mean that every field that I have forced to uppercase at
table design time will have to have a trigger added? I use a bunch of fields
forced to uppercase. It was kind of nice to always know the resultant field
was uppercase, even when I didn't remember to code anything special for the
field. I'm sure I can adapt, but was this change due to SQL 2003
specifications? I look forward to seeing all the "what's new" and "what's
different" documents.

-Johnnie

Sun, Dec 17 2006 4:26 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Johnnie,

<< Does this basically mean that every field that I have forced to uppercase
at table design time will have to have a trigger added? I use a bunch of
fields forced to uppercase. It was kind of nice to always know the resultant
field was uppercase, even when I didn't remember to code anything special
for the field. I'm sure I can adapt, but was this change due to SQL 2003
specifications? >>

Primarily, yes.  We took the syntax back to standard SQL:2003 levels and
will be adding back items that we want to keep.  DBISAM had so many
extensions that were non-standard that it was easier to just scrap the whole
thing and start from the standard instead of trying to reconcile them all.

--
Tim Young
Elevate Software
www.elevatesoft.com

Image