RE: [HACKERS] Get OID of just inserted record
От | Ansley, Michael |
---|---|
Тема | RE: [HACKERS] Get OID of just inserted record |
Дата | |
Msg-id | 1BF7C7482189D211B03F00805F8527F748C1FB@S-NATH-EXCH2 обсуждение исходный текст |
Ответы |
Re: [HACKERS] Get OID of just inserted record
|
Список | pgsql-hackers |
Well, with autocommit on, the statement would fail, and I would expect the insert to then roll back, if the select part failed. No problem, really. MikeA -----Original Message----- From: D'Arcy" "J.M." Cain To: aaron@gtv.ca Cc: peter_e@gmx.net; e99re41@DoCS.UU.SE; pgsql-hackers@postgreSQL.org Sent: 11/3/99 5:04 AM Subject: Re: [HACKERS] Get OID of just inserted record Thus spake Aaron J. Seigo > > => insert into foo values (4, 'aaa'); > > INSERT 7998067 1 > > this assumes that one is using libpq.. it would be nice to have access to this > from psql or anywhere for that matter.. and not just oids.. but, say for > instance, default values in tables that are generated dynamically... etc Just to see if I understand you, is this what you want to be able to do? UPDATE t1 SET other_oid = (INSERT INTO t2 VALUES (1, 'aaa') RETURN OID) WHERE someting = 'something'; or SELECT (INSERT INTO t2 (f1, f2) VALUES (1, 'aaa') RETURN f3); In other words, sub-inserts. It is kind of a neat idea. I don't know that it is worth spending much time on but it would be a neat feature that no one else has. Just wondering, how would you handle insert only tables? That is, you have insert privleges but not select. Would you still return the field or fields requested surprising the database designer, accept the insert but return an error or refuse the insert entirely since the task could not be completed? -- D'Arcy J.M. Cain <darcy@{druid|vex}.net> | Democracy is three wolves http://www.druid.net/darcy/ | and a sheep voting on +1 416 425 1212 (DoD#0082) (eNTP) | what's for dinner. ************
В списке pgsql-hackers по дате отправления: