ADMIN

* Allow international error message support and add error codes

The JDBC driver already has the international error message support. All
it needs are some translations of the errors.properties file.

It would be easy to add error codes to it.

TYPES

* Large objects
	o Fix large object mapping scheme, own typeid or reltype(Peter)
	o Allow large text type to use large objects(Peter)

I hope to these two done for 6.6

	o Not to stuff everything as files in a single directory, hash
dirs
	o Allow large object vacuuming

Do you mean vacuuming within a large objects table, or removing orphaned
ones?
A solution for orphaning is in contrib, although it still needs some
work.

On the JDBC front, I'm planning for 6.6:

* Array support
* Large Object Stream support
* More JDBC2 API implemented

But the big one will be to get the driver to use the current protocol.
Up until now, it's been using the 6.3 backend protocol. Now that the
current driver supports JDBC2, I want to get it up to date.

This will mean that the 6.6 driver will not be backward compatible with
earlier backends (I can't remember which one started using the current
protocol). The 6.5 driver does support 6.3 and 6.4.x backends.

Peter

-- 
Peter Mount
Enterprise Support
Maidstone Borough Council
Any views stated are my own, and not those of Maidstone Borough Council.


Thu, 8 Jul 1999 09:30:24 +0100 
Peter Mount <petermount@it.maidstone.gov.uk>
RE: [HACKERS] Updated TODO list
> ADMIN
> 
> * Allow international error message support and add error codes
> 
> The JDBC driver already has the international error message support. All
> it needs are some translations of the errors.properties file.
> 
> It would be easy to add error codes to it.

Good.  I think Vadim wasn't codes from the backend for scripts and
stuff.

> 
> TYPES
> 
> * Large objects
> 	o Fix large object mapping scheme, own typeid or reltype(Peter)
> 	o Allow large text type to use large objects(Peter)
> 
> I hope to these two done for 6.6

Good. I can help too.

> 
> 	o Not to stuff everything as files in a single directory, hash
> dirs
> 	o Allow large object vacuuming

> Do you mean vacuuming within a large objects table, or removing orphaned
> ones?

Tom Lane says you can get multiple versions of a large object in the
file, and there is no way to remove them.

> A solution for orphaning is in contrib, although it still needs some
> work.
> 
> On the JDBC front, I'm planning for 6.6:
> 
> * Array support
> * Large Object Stream support
> * More JDBC2 API implemented
> 
> But the big one will be to get the driver to use the current protocol.
> Up until now, it's been using the 6.3 backend protocol. Now that the
> current driver supports JDBC2, I want to get it up to date.

Cool.

> This will mean that the 6.6 driver will not be backward compatible with
> earlier backends (I can't remember which one started using the current
> protocol). The 6.5 driver does support 6.3 and 6.4.x backends.

That is not a problem.  We have given them enough releases that will
work with the new driver.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

Thu, 8 Jul 1999 11:45:10 -0400 (EDT)
Bruce Momjian <maillist@candle.pha.pa.us>
Re: [HACKERS] Updated TODO list