Thread
-
ODBC 7.1
Keith Gray <keith@heart.com.au> — 2001-08-10T02:33:27Z
Greetings All, Is this the correct forum to discuss ODBC driver issues? I have a Linux/PostgreSQL server which has been upgraded to run 7.1 - the main reason was to be able to use the TOAST extensions. We have some documentation attached to fields which is up to 64kb. After upgrading the server I installed the current (7.1) ODBC driver for Win32. It now seems that concurrent table writes are limited? My write times are fairly slow. (significantly slower than 6.4/7.0) Some tables which are updated simultaneously - like sales and general ledger are not staying in synch. Any suggestions would be welcomed (including upgrades) -- Keith Gray Technical Development Manager Heart Consulting Services P/L mailto:keith@heart.com.au
-
Re: [SQL] ODBC 7.1
Hiroshi Inoue <inoue@tpf.co.jp> — 2001-08-10T02:57:43Z
Keith Gray wrote: > > Greetings All, > > Is this the correct forum to discuss ODBC driver issues? > No, pgsql-odbc is the right forum. > I have a Linux/PostgreSQL server which has been upgraded > to run 7.1 - the main reason was to be able to use the > TOAST extensions. We have some documentation attached > to fields which is up to 64kb. > > After upgrading the server I installed the current (7.1) > ODBC driver for Win32. > Is the version 7.01.0006 ? > It now seems that concurrent table writes are limited? > > My write times are fairly slow. (significantly slower > than 6.4/7.0) > Is the comparison for the < 8k data ? Is it as fast as 6.4/7.0 except concurrent write ? regards, Hiroshi Inoue
-
Re: ODBC 7.1
Keith Gray <keith@heart.com.au> — 2001-08-10T03:06:52Z
Hiroshi Inoue wrote: > > Keith Gray wrote: > > > > TOAST extensions. We have some documentation attached > > to fields which is up to 64kb. > > > > After upgrading the server I installed the current (7.1) > > ODBC driver for Win32. > > > > Is the version 7.01.0006 ? No... 7.01.0005 > > My write times are fairly slow. (significantly slower > > than 6.4/7.0) > Is the comparison for the < 8k data ? Without the large text attachment. > Is it as fast as 6.4/7.0 except concurrent write ? Not sure... lookups/queries are great (indexed and vacuum-analyzed) I think the write is slow... (and unsuccessful) because of a time-out. -- Keith Gray Technical Development Manager Heart Consulting Services P/L mailto:keith@heart.com.au
-
Re: ODBC 7.1
Hiroshi Inoue <inoue@tpf.co.jp> — 2001-08-10T03:19:03Z
Keith Gray wrote: > > Hiroshi Inoue wrote: > > > > Keith Gray wrote: > > > > > > TOAST extensions. We have some documentation attached > > > to fields which is up to 64kb. > > > > > > After upgrading the server I installed the current (7.1) > > > ODBC driver for Win32. > > > > > > > Is the version 7.01.0006 ? > > No... 7.01.0005 Please download the latest driver 7.01.0006. Other drivers couldn't handle text fields > 8k. > > > > My write times are fairly slow. (significantly slower > > > than 6.4/7.0) > > > Is the comparison for the < 8k data ? > > Without the large text attachment. > > > Is it as fast as 6.4/7.0 except concurrent write ? > > Not sure... lookups/queries are great (indexed and > vacuum-analyzed) I think the write is slow... (and > unsuccessful) because of a time-out. Are you checking the 'Text as LongVarChar' driver option ? regards, Hiroshi Inoue
-
INSERT FOLLOW WITH OTHER INSERT
Johny Jugianto <johny.q@rocketmail.com> — 2001-08-10T03:43:16Z
hi all i have a table like this CREATE SEQUENCE seq_student_id INCREMENT 1 START 1; CREATE TABLE students ( student_id INT4 NOT NULL DEFAULT NEXTVAL('seq_student_id'), student_name text, student_address text, primary key(student_id) ) CREATE TABLE student_club ( student_id INT4 NOT NULL; club_id INT4, CONSTRAINT student_id_update FOREIGN KEY(student_id) REFERENCES students(student_id) ON UPDATE CASCADE ) my question is how i can make auto insert student_id on table student_club when i insert into table students example: INSERT INTO students(student_name) VALUES('Willy'); table STUDENT student_id | name | address --------------------------------- 1 | Willy | and on TABLE student_club student_id | club_id -------------------- 1 | i have trying with create rule and with check_foreign_key, but i haven't found solution. anyone can help me? Thanks in advance __________________________________________________ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/ -
Re: INSERT FOLLOW WITH OTHER INSERT
Bhuvan A <bhuvansql@yahoo.com> — 2001-08-10T11:17:18Z
Are you ready to solve your problem using a trigger and 'plpgsql' function ?? .. then proceed .. trigger :) +++++++++++++++++++++++++++++++++++++++++++ CREATE TRIGGER trigger_student_club before INSERT OR UPDATE ON students FOR EACH ROW EXECUTE PROCEDURE ins_student_club_func(); +++++++++++++++++++++++++++++++++++++++++++ function :) +++++++++++++++++++++++++++++++++++++++++++ CREATE FUNCTION ins_student_club_func() RETURNS OPAQUE AS 'BEGIN INSERT INTO student_club(student_id) VALUES (new.student_id); return new; END;' LANGUAGE 'plpgsql'; +++++++++++++++++++++++++++++++++++++++++++ Hope it works. :) Regards, Bhuvaneswar. On Aug 9, Johny Jugianto wrote: > hi all > > i have a table like this > > CREATE SEQUENCE seq_student_id INCREMENT 1 START 1; > CREATE TABLE students ( > student_id INT4 NOT NULL DEFAULT > NEXTVAL('seq_student_id'), > student_name text, > student_address text, > primary key(student_id) > ) > CREATE TABLE student_club ( > student_id INT4 NOT NULL; > club_id INT4, > CONSTRAINT student_id_update FOREIGN KEY(student_id) > REFERENCES students(student_id) ON UPDATE CASCADE > ) > > my question is how i can make auto insert student_id > on table student_club when i insert into table > students > > example: > INSERT INTO students(student_name) VALUES('Willy'); > > table STUDENT > student_id | name | address > --------------------------------- > 1 | Willy | > > and on TABLE student_club > student_id | club_id > -------------------- > 1 | > > > i have trying with create rule and with > check_foreign_key, but i haven't found solution. > anyone can help me? > > Thanks in advance > > > __________________________________________________ > Do You Yahoo!? > Make international calls for as low as $.04/minute with Yahoo! Messenger > http://phonecard.yahoo.com/ > > ---------------------------(end of broadcast)--------------------------- > TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org > -
Re: ODBC 7.1
Keith Gray <keith@heart.com.au> — 2001-08-14T02:14:02Z
Hiroshi Inoue wrote: > > Keith Gray wrote: > > > Please download the latest driver 7.01.0006. > Other drivers couldn't handle text fields > 8k. Done that now... > Are you checking the 'Text as LongVarChar' driver option ? Yes. It doesn't look like an ODBC issue now... I have tried all ODBC drivers 6.4, 7.0 and 7.1 with less than 8kb fields and they all seem to have this same problem with timeout. To me this seems like a 7.1 database issue we didn't seem to have with 6.4 and 7.0 Not sure what the timeout is, but I assume a lock condition. -- Keith Gray Technical Development Manager Heart Consulting Services P/L mailto:keith@heart.com.au