Thread: AW: [HACKERS] char types gone.

AW: [HACKERS] char types gone.

From
Zeugswetter Andreas
Date:
> 1. Regression tests make very extensive use of char16.  Seems to
> me that these should be changed to a name.  Same for tutorial and
> any other example references in the code.  Seem ok?

** down sinks the mast of the old postquel, there, can you see it blink in the deep green water ? **
** nostalgia on my face **  I think I forgot to mention my nicest hobby, sailing **

I think char(16) would be the correct replacement in the regression tests
and tutorial, since this is what we want people to use. name is more or less
an internal type for system catalogs and the like. I would not propagate it too much.
Of course regress.c would need a little patch then, but no big deal.

Andreas



Re: AW: [HACKERS] char types gone.

From
The Hermit Hacker
Date:
On Mon, 23 Mar 1998, Zeugswetter Andreas wrote:

> > 1. Regression tests make very extensive use of char16.  Seems to
> > me that these should be changed to a name.  Same for tutorial and
> > any other example references in the code.  Seem ok?
>
> ** down sinks the mast of the old postquel, there, can you see it blink
> in the deep green water ? ** ** nostalgia on my face ** I think I forgot
> to mention my nicest hobby, sailing **

    Okay, this one has me...what benefit is there to char16 over
char(16)?  Why, in the first place, was it implemented as char16 anyway?

    As for "down sinks the mast"...so far as I've been able to tell,
we have *never* removed anything that wasn't replaced by a better way of
doing it (time travel with triggers)...we didn't leave anyone floundering
for a solution to it, we provided it...but now, its not forced on
*everyone*, just on those databases/tables that require it...

    Same functionality, better performance...





Re: AW: [HACKERS] char types gone.

From
"Thomas G. Lockhart"
Date:
> As for "down sinks the mast"...so far as I've been able to tell,
> we have *never* removed anything that wasn't replaced by a better way
> of doing it (time travel with triggers)...we didn't leave anyone
> floundering for a solution to it, we provided it...but now, its not
> forced on *everyone*, just on those databases/tables that require
> it...
>         Same functionality, better performance...

Ah, he wasn't complaining, just saluting a retiring soldier :)