> Dear Sir/Madam,
> I'm a PhD student at Essex University in UK, doing a research in Distributed
> Database Systems. I would like to ask you some questions:
> I'm using Postgres ver.7, installed in Linux lab which consists of 25
> terminals.
> My actual question is if Postgres provides the functio
Postgres has an 'ascii' function that converts
characters to ascii, values, but it appears to be a
one way street. I can't find a way to convert ascii
values to characters, like 'chr' in Oracle. Anyone
know how to do this?
-Alex
__
Do You Yahoo!?
> INteresting,
> that I tried to find out what cause the problem just compiling
> backend/utils/adt/ with -funsigned-char option but this won't help.
> I thought (as in earlier time) locale-aware code are in this
> directory. The problem already exists in 6.5 release,
> so I'm not sure recent
Bruce Momjian writes:
> Sounds like people want it. Can you polish it off, add SGML docs and
> send it over?
> > There's a config file /etc/pg_service.conf, having an entry like:
Please check that the final patch uses a file in ${sysconfdir} that was
specified at configure time, and not "/etc"
I know that this feature is often asked for, but be aware that it is
incompatible with the future, namely SQL schema support. Under that
scheme, a schema has an owner and all objects belong to a schema. I guess
at that point we'd have to disable this command with a reference to some
sort of comman
INteresting,
that I tried to find out what cause the problem just compiling
backend/utils/adt/ with -funsigned-char option but this won't help.
I thought (as in earlier time) locale-aware code are in this
directory. The problem already exists in 6.5 release,
so I'm not sure recent Peter's chan
The named directory seems to be the fossile of a prehistoric regression
test, last updated 1996. It seems to be completely outdated, is there any
need to keep this?
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
Oleg Bartunov <[EMAIL PROTECTED]> writes:
It's clear that we must use 'unsigned char' instead of 'char'
and corrected version runs ok on both systems. That's why I suspect
that gcc 2.95.2 has different default under FreeBSD which could
cause problem with LC_CTYPE in 7.0.2
>>
On Sat, 16 Sep 2000, Tom Lane wrote:
> Date: Sat, 16 Sep 2000 11:23:33 -0400
> From: Tom Lane <[EMAIL PROTECTED]>
> To: Oleg Bartunov <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
> Subject: Re: [HACKERS] broken locale in 7.0.2 without multibyte support (FreeBSD
>4.1-RELEASE) ?
Oleg Bartunov <[EMAIL PROTECTED]> writes:
> It's clear that we must use 'unsigned char' instead of 'char'
> and corrected version runs ok on both systems. That's why I suspect
> that gcc 2.95.2 has different default under FreeBSD which could
> cause problem with LC_CTYPE in 7.0.2
> I didn't test
Hi,
I am tring to use the qnx version of postgresql
7.0.0
I have qnx 4.25 and TCP/IP
I have compiled postgres using
gcc
I have installed it.
then I have started postgres with -D and -i
options.
The only commad that I can execute is initdb.
When I execute any other command I hav
Hi,
while I'm doing more accurate test I just want to ask if
somebody test locale in 7.0.2 under FreeBSD ?
the point is that I usually compile postgres with
--enable-locale --enable-multibyte and never had a problem
with locale. Today I decided to use only --enable-locale
and found that LC_CTYP
Jan Wieck wrote:
>
> Hey, look at the headline:
>
> Linux Magazine's Editor's Choice Awards
> by The Editors of Linux Magazine
>
> The Linux market is exploding with all kinds of
> great new (and old) products. We decided it was
> time to round up our
Am Die, 12 Sep 2000 schrieb Bruce Momjian:
> Sounds like people want it. Can you polish it off, add SGML docs and
> send it over?
I prepared and tested a patch vs. 7.0.2, and it works fine. I've added
another option which allows users to have their own service file in
~/.pg_service.conf, which
14 matches
Mail list logo
