Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: BIGINT support?
Howard J. Rogers wrote:
>
> "Frank van Bortel" <fvanbortel_at_netscape.net> wrote in message
> news:c3hc26$6to$1_at_news1.tilbu1.nb.home.nl...
> > Kenneth wrote:
> > > On Fri, 19 Mar 2004 15:14:21 +0100, Frank van Bortel
> > > <fvanbortel_at_netscape.net> wrote:
> > >
> > >
> > >>Kenneth wrote:
> > >>
> > >>
> > >>>I checked your URL which stated that a VARCHAR2 column can hold 4K of
> > >>>chars. Not true, 4K = 4 * 1024 = 4096. A VARCHAR2 can only hold 4000
> > >>>chars.
> > >>>
> > >>
> > >>And not even that is true, it can hold up to 4000 byte of characters.
> > >
> > >
> > > Yep. Which results in a maximum of 4000 chars with a single-byte
> > > charset. As I said.
> > >
> > > - Kenneth Koenraadt
> > >
> > >
> > >
> > >
> > >>--
> > >>
> > >>Regards,
> > >>Frank van Bortel
> > >>
> > >
> > >
> > You did not mention the single-byte charset, which causes confusion
> > when just stating a varchar2(4000) column can hold 4000 characters.
> >
> > The whole point is, it's not characters, it's bytes.
>
> Well, if I was to be picky, in 9i it depends on what the setting of your
> NLS_LENGTH_SEMANTICS is as to whether its characters or bytes. But it
> defaults to 'BYTE', and the data dictionary is always 'BYTE', regardless of
> the parameter setting. So I know what you were driving at.
>
> Regards
> HJR
This may have been fixed by now, but for a long time in v9, if you
connect as sysdba and run a DESC on v$vpd_policy, you'll it has a column
defined as VARCHAR2(4096)
:-O -- -------------------------------