Re: [HACKERS] Regarding column reordering project for GSoc 2012

2012-03-25 Thread Claes Jakobsson
On 19 mar 2012, at 22.45, Merlin Moncure wrote:
 one pl/java based project that IMO is just screaming to be done is a
 pl/java based FDW (wrapping JDBC) that would approximately reproduce
 dblink...maybe with some extra features geared towards ETL type jobs
 like a row based callback for transformations in java.

Personally I'd love a type 2 JDBC driver for PostgreSQL. It should be feasible 
as a summer project. It's somewhere deep down on my TODO list so I'd be happy 
to help.

Cheers,
Claes 
-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers


Re: [HACKERS] Regarding column reordering project for GSoc 2012

2012-03-25 Thread Claes Jakobsson

On 20 mar 2012, at 13.08, Heikki Linnakangas wrote:
 On 20.03.2012 11:10, Claes Jakobsson wrote:
 
 Personally I'd love a type 2 JDBC driver for PostgreSQL.
 
 Why?

listen/notify over SSL for example unless that's been fixed in the JDBC driver 
recently. And I'm sure there are other things in libpq that would be nice to 
have.

As mainly a Perl dude which uses libpq via DBD::Pg I find it odd that the Java 
people doesn't do the same instead of reimplementing everything.

Cheers,
/Claes


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers


Re: [HACKERS] JSON for PG 9.2

2011-12-20 Thread Claes Jakobsson
On Dec 20, 2011, at 12:39 AM, David E. Wheeler wrote:
 On Dec 19, 2011, at 2:49 AM, Dimitri Fontaine wrote:
 
 My understanding is that JSON is a subset of ECMAscript
 
 Well, no, JSON is formally “a lightweight data-interchange format.” It’s 
 derived from JavaScript syntax, but it is not a programming language, so I 
 wouldn’t say it was accurate to describe it as a subset of JS or ECMAScript.
 
  http://json.org/

Are people explicitly asking for a) *JSON* datatype or b) a type that lets you 
store arbitrary complex semi-untyped data structures?

if b) then this might get a lot more interesting

Cheers,
Claes
-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers