Hi all,
I have a question of PostgreSQL's floating point
representation.
create table t (fl1 float4, fl2 float4, fl3 float4);
insert into t values (1.234567, 1.23457, 1.23457);
select * from t;
fl1 | fl2 | fl3
-+-+-
1.23457 | 1.23457 | 1.23457
(1 row)
select *
On Wed, 14 Feb 2001, Peter Eisentraut wrote:
> Tom Lane writes:
>
> > Thomas Lockhart <[EMAIL PROTECTED]> writes:
> > > Also, could the "-F" option be disabled now that WAL is enabled? Or is
> > > there still some reason to encourage/allow folks to use it?
> >
> > I was the one who put it back i
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> Oh, I see. So the question still remains: can a MULTIBYTE-aware backend
> ever use a sort order different from strcmp() order? (That is, not as
> a result of LOCALE, but just because of the non-SQL-ASCII encoding.)
>>
>> According to the code, no, beca
> Tom Lane writes:
>
> > Oh, I see. So the question still remains: can a MULTIBYTE-aware backend
> > ever use a sort order different from strcmp() order? (That is, not as
> > a result of LOCALE, but just because of the non-SQL-ASCII encoding.)
>
> According to the code, no, because varstr_cmp(
While working on fixing the ODBC driver, I did several things I should
not have done during beta. First, I removed the feature that allowed
ODBC to talk to backends of version <=6.3. This should not have been
done during beta. I did this very quickly, with little warning to
users. Second, I pg
Fred Yankowski writes:
> What do you see in our plan that implies "vast sections of
> platform-specific code" "littering the backend"? If such changes are
> necessary, I want to know before we embark on this work.
>
> As far as this being "optional functional[ity]", I contend that
> PostgreSQL h
Tom Lane writes:
> Oh, I see. So the question still remains: can a MULTIBYTE-aware backend
> ever use a sort order different from strcmp() order? (That is, not as
> a result of LOCALE, but just because of the non-SQL-ASCII encoding.)
According to the code, no, because varstr_cmp() doesn't pay
<[EMAIL PROTECTED]> writes:
> So i use the following query in order to have default operator:
> INSERT INTO pg_opclass(opcname,opcdeftype) select 'ean13_ops',oid
> from pg_type where typname = 'ean13' ;
> So the new error with postgresql when i try to create an index
> on my new type is : opclass
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
>> Okay, so if a database has been built by a backend that knows MULTIBYTE
>> and has some "yomigana" info available, then indexes in text columns
>> will not be in the same order that strcmp() would put them in, right?
> No. The "yomigana" exists in the a
> Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> > If we sort these strings using strcmp(), we would get:
> > ...
> > This result might not be perfect, but resonable for most cases since
> > the code value of each character in EUC_JP is defined in the hope that
> > it can be sorted by its phisical val
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> If we sort these strings using strcmp(), we would get:
> ...
> This result might not be perfect, but resonable for most cases since
> the code value of each character in EUC_JP is defined in the hope that
> it can be sorted by its phisical value.
> If we
Error 500: Internal Server Error.
Someone did bad.
Gavin
Bruce Momjian wrote:
>
> Does anyone know why the MySQL web site is missing:
>
> http://www.tcx.se/
>
> It shows an empty page. Did they just close it?
Try http://www.mysql.com/.
-Egon
--
SIX Offene Systeme GmbH ·Stuttgart - Berlin
Sielminger Straße 63 ·D-707
Does anyone know why the MySQL web site is missing:
http://www.tcx.se/
It shows an empty page. Did they just close it?
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830
Done.
> Bruce, could you update following in HISTORY:
>
> Allow automatic conversion to Unicode (Tatsuo)
>
> to:
>
> Allow automatic conversion to/from Unicode (Tatsuo, Eiji)
>
> Eiji Tokuya <[EMAIL PROTECTED]> has contributed a better
> conversion map for SJIS.
> --
> Tatsuo Ishii
>
--
Hi,
Well i create a new type. I want indexing my new type but i
can't , postgresql erro : my type has no default operator class
So i use the following query in order to have default operator:
INSERT INTO pg_opclass(opcname,opcdeftype) select 'ean13_ops',oid
from pg_type where typname = 'ean13' ;
Title: RE: [HACKERS] Postgre SQL for Windows
There is a link to sqlSQL for win32 here http://208.160.255.143/pgsql/pgsql.exe . Not tried it yet but it has been posted here before.
Regards
Ben
> -Original Message-
> From: Peter T Mount [mailto:[EMAIL PROTECTED]]
> Sent: 06 Februar
Bruce, could you update following in HISTORY:
Allow automatic conversion to Unicode (Tatsuo)
to:
Allow automatic conversion to/from Unicode (Tatsuo, Eiji)
Eiji Tokuya <[EMAIL PROTECTED]> has contributed a better
conversion map for SJIS.
--
Tatsuo Ishii
> >> Are these encodings all guaranteed to have the same collation order as
> >> SQL_ASCII?
>
> > Yes & no.
>
> Um, I'm confused ...
>
> >> If not, we have the same index corruption issues as for LOCALE.
>
> > If the backend is configued with LOCALE enabled and the database is
> > not configu
19 matches
Mail list logo
