Irc channel?? / converting from Oracle

[ Charset ISO-8859-1 unsupported, converting... ]

I tried using the #postgres channel on efnet (various servers), is that
channel very active? what times does it get traffic?? I tried sitting there
the other day and someone (a bot?) was kicking everyone after 1 minute
idle...?

It is #postgresql, and there are usually about 14 people on it.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

#postgres was a project out of University of California @ Berkeley some 5+
years ago ... as far as I know, its no longer being developed, but I could
be wrong ...

PostgreSQL is based off of that project, and ppl keep mistakenly refer to
it as such, which tends to sadly confuse new ppl :(

on efnet, its #PostgreSQL

On Thu, 18 Jan 2001, bmatthewtaylor_Yahoo wrote:

I tried using the #postgres channel on efnet (various servers), is that
channel very active? what times does it get traffic?? I tried sitting there
the other day and someone (a bot?) was kicking everyone after 1 minute
idle...?

I'm currently converting a system from Oracle to Postgresql, the original
design used only simple sequences/triggers (now moved across to sequences in
pgsql) with the majority of the work in java servlets. (providing web
interface) seems to be coming together nicely.

few little things I found useful.
- the syntax below works in Oracle and Postgresql

create table sample(
attrib1 varchar(20),
attrib2 numeric, --results in default numeric(30,6)
being generated
attrib3 numeric(5), --results in numeric(5,0)
constraint some_name_u_choose primary key(attrib1),
constraint some_name_u_choose2 foreign key table_name(attrib_name)
);

select sysdate from dual;
in Oracle gets replaced with
select current_timestamp
in Postgres. (refer the postgres manual, an excellent document!!!)

select to_char(current_timestamp, 'dd-mm-yyyy');
formats dates in dd-mm-yyyy format (or use Mon to get Jan, Feb etc)

Q: does anyone know where the standard syntax for this is defined? is this a
SQL92 standard? (I've previously picked this up from my Oracle manuals)

I'm looking at using asp, since a number of colleagues have mentioned they
find signicicent reductions in devel time... any comments? (off topic I
suspect)

so far I've had no major problems and been very impressed (installed 7.0.3
RPM on linux 6.2)

Matthew
(Brisbane Australia)

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org

hi all,
Does postgres support other character sets?
We've been thinking in porting an application to chinesse, but we don't
know if it's possible to store chinesse characters in postgres

TIA

--Yohans

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Yohans Mendoza System Analyst
yohans@sirius-images.com Sirius Images Inc.
http://www.sirius-images.net/users/yohans http://www.sirius-images.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

hi all,
Does postgres support other character sets?
We've been thinking in porting an application to chinesse, but we don't
know if it's possible to store chinesse characters in postgres

I don't know what kind of Chinese are talking about, but PostgreSQL
does support both tradional Chinese and simplified Chinese.

tradional Chinese: EUC-CN

simplified Chinese: EUC-TW (you could use Big5 for clients
only. PostgreSQL will do automatic conversion between Big5 and EUC-TW,
in this case)

ALso, you could use UNICODE(UTF-8). For upcomming 7.1, PostgreSQL will
provide automatic conversion between:

UTF-8 <--> EUC-CN
UTF-8 <--> EUC-TW
UTF-8 <--> Big5
--
Tatsuo Ishii

On Fri, Jan 19, 2001 at 10:22:42AM +0900, Tatsuo Ishii wrote:
...

ALso, you could use UNICODE(UTF-8). For upcomming 7.1, PostgreSQL will
provide automatic conversion between:

UTF-8 <--> EUC-CN
UTF-8 <--> EUC-TW
UTF-8 <--> Big5

Out of interest, does --enable-recode do anything if you don't have
--enable-multibyte? I would be interested in say

ISO8859-1 <--> ISO8859-2

but without the overhead of wide chars..

Cheers,

Patrick