Re: [HACKERS] [GENERAL] Using oids

2003-09-03 Thread Ashley Cambrell
ementing oracl type binding? Ala http://groups.google.com.au/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&th=5cc63a569577d024#link2 With the new FE/BE changes, how easy would it be to implement? (I mentioned it the FE/BE discussions) Ashley Cambrell -

Re: [HACKERS] Roadmap for FE/BE protocol redesign

2003-03-10 Thread Ashley Cambrell
Neil Conway wrote: On Mon, 2003-03-10 at 16:37, Ashley Cambrell wrote: This would also get around the problem of getting values from newly inserted rows (eg PKs) without resorting to OIDs. That's not a problem: ensure that the newly inserted row has a SERIAL c

Re: [HACKERS] Roadmap for FE/BE protocol redesign

2003-03-10 Thread Ashley Cambrell
he problem of getting values from newly inserted rows (eg PKs) without resorting to OIDs. Not entirely a FE/BE issue... but worth considering in any redesign. Ashley Cambrell ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: [HACKERS] default to WITHOUT OIDS?

2003-01-10 Thread Ashley Cambrell
Neil Conway wrote: On Fri, 2003-01-10 at 18:17, Ashley Cambrell wrote: The problem with getting rid of OIDs as default is there is then no way to get the primary key of a just inserted row with out OIDs (as far as I know) Use currval() on the PK sequence -- if you call

Re: [HACKERS] default to WITHOUT OIDS?

2003-01-10 Thread Ashley Cambrell
ql = "INSERT INTO testtable(test_id, text1) "; $sql .= "VALUES(test_id_seq.nextval, :text1) RETURNING test_id INTO :test_id"; $stmt = ociparse($conn,$sql); ocibindbyname($stmt, :text1) &$some_str, -1); ocibindbyname($stmt, ':test_id', &$test

Re: [HACKERS] tweaking MemSet() performance

2002-08-30 Thread Ashley Cambrell
() *1024 2m44.609s MemSet() *1024  3m14.567s memset() *2048 5m12.630s MemSet() *2048  6m24.916s memset() *4096 10m8.183s MemSet() *4096 12m43.830s Ashley Cambrell

Re: [HACKERS] 7.3 schedule

2002-04-11 Thread Ashley Cambrell
Neil Conway wrote: >On Thu, 11 Apr 2002 16:25:24 +1000 >"Ashley Cambrell" <[EMAIL PROTECTED]> wrote: > >>What are the chances that the BE/FE will be altered to take advantage of >>prepare / execute? Or is it something that will "never happen"? &g

Re: [HACKERS] 7.3 schedule

2002-04-10 Thread Ashley Cambrell
tical path is Tom's schema support. > >We'll need a good beta period this time, because of: > >* Schemas >* Prepare/Execute maybe > What are the chances that the BE/FE will be altered to take advantage of prepare / execute? Or is it something that will "never ha

Re: OID wraparound (was Re: [HACKERS] pg_depend)

2001-07-18 Thread Ashley Cambrell
solve the problem of having a unique identifier returned for inserts. I'm sure it would please quite a few people in the process, especially ones moving across from Oracle. (kill two birds with one stone) > > regards, tom lane > Ashley Cambrell ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster

Re: [HACKERS] Version data type. - DONE

2000-10-04 Thread Ashley Cambrell
, but it's still useful... (and I don't know enough about Postgres's internals to know if it's "done right" (tm).) Ashley Cambrell Ashley Cambrell wrote: > Hi all, > > Just wondering if anyone has already created a version data type where > 1.100

[HACKERS] Version data type.

2000-10-03 Thread Ashley Cambrell
27;s work on arrays Thank You Ashley Cambrell