Re: type unknown - how important is it? - Mailing list pgsql-hackers

From Shachar Shemesh
Subject Re: type unknown - how important is it?
Date
Msg-id 42392B3D.4070904@shemesh.biz
Whole thread Raw
In response to Re: type unknown - how important is it?  (Dave Cramer <pg@fastcrypt.com>)
Responses Re: type unknown - how important is it?
Re: type unknown - how important is it?
List pgsql-hackers
Dave Cramer wrote:

> Shachar,
>
> I think with type oid 705 (unknown) it's safe to treat it as text. 
> Certainly better than punting.

Question is what DBTYPE to report it as. Options are DBTYPE_WSTR (UTF-16 
string, which means the input string must be a valid UTF-8 string), 
DBTYPE_STR (just dump it as I get it, and hope that client doesn't barf 
on the UTF-8 encoding), DBTYPE_BYTES (it's an array of bytes, just let 
the client figure out what to do with it. No promises on my part).

I don't know type 705 well enough to decide which would work best. If 
it's guaranteed to be a validly encoded text string, then I'll just put 
it in as DBTYPE_WSTR, and get it done with.

> On another note are you aware of any issues with transactions? 
> Specifically with using the dated autocommit mode ?

I'm not sure what dated autocommit is. What are the issues you are seeing?

> Dave
      Shachar

-- 
Shachar Shemesh
Lingnu Open Source Consulting ltd.
Have you backed up today's work? http://www.lingnu.com/backup.html



pgsql-hackers by date:

Previous
From: "Marc G. Fournier"
Date:
Subject: Re: Changing the default wal_sync_method to open_sync for
Next
From: Ali Baba
Date:
Subject: Exception handiling