Re: [BUGS] BUG #1986: Please include ONE BIG .txt and .HTML file in *docs*.tar.gz
> > This ONE BIG file will help loading it off-line to a web > browser (or > > editor *.txt), and to make quick searches on backward and forward. > > This wouldn't be hard to implement. Are others interested in this? The original bug talked about Windows - I'd just like to add that on Windows we will already do this on 8.1, in the form of a CHM file. That doesn't mean we shouldn't do sometihng for other platforms, though ;-) //Magnus ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[BUGS] BUG #1989: Curious blob problem
The following bug has been logged online: Bug reference: 1989 Logged by: Petr Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0 Operating system: Win 2003 Description:Curious blob problem Details: Hi. I'm trying to use blob fields (bytea) and have a curious problem with it (in Delphi). When i'm store the blob stream into DB, the length is 810 bytes. When i'm trying to get data from DB, gives me only 807 bytes. I was try to store entire streams into files and locate differences. Three bytes aren't be in exported file in the middle of the file :-O. Can you look at this problem (i can send you these files). PS : sorry for my poor english. Petr ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [BUGS] BUG #1986: Please include ONE BIG .txt and .HTML file in *docs*.tar.gz
| Peter Eisentraut writes: | > Am Freitag, 21. Oktober 2005 17:31 schrieb Jari Aalto: | >> This ONE BIG file will help loading it off-line to | >> a web browser (or editor *.txt), and to make quick searches on backward and | >> forward. | | > This wouldn't be hard to implement. Are others interested in this? | | I'd object to bloating the tarball itself with two redundant copies of | the documentation ... especially on the basis of only one request. | But couldn't we make such a version available for separate download | by those who want it? Thanks fo taking this issue forward. It would increase the archive much because html and text files compress extremely well. The logical place for the documentation, is the "doc" package that already includes FAQ. Perhaps you meant to separate: - pure source (*.sgml): *-doc-source.tar.gz - generated files: *-doc-generated.tar.gz Jari ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[BUGS] BUG #1988: keygen not implemented
The following bug has been logged online: Bug reference: 1988 Logged by: Mike Clements Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.3 Operating system: WinXP Description:keygen not implemented Details: Create a table with an integer primary key using a sequence to automatically assign values. Connect to the database with a JDBC client. Insert a row into the table using: Connection.prepareStatement(sql, Statement.RETURN_GENERATED_KEYS); The driver throws an exception saying this method is not yet implemented. What it should do is create the prepared statement so when you execute it, the returned ResultSet has the generated primary key. ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[BUGS] BUG #1987: UTF8 encoding differences hamper upgrades
The following bug has been logged online: Bug reference: 1987 Logged by: Paul Lindner Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1beta3 Operating system: Fedora Core 4 x86_64 Description:UTF8 encoding differences hamper upgrades Details: I've been doing some test imports of UNICODE databases into Postgres 8.1beta3. The only problem I've seen is that some data from 8.0 databases will not import. I've generated dumps using pg_dump from 8.0 and 8.1. Attempting to restore these results in Invalid UNICODE byte sequence detected near byte ... Question: Does the 8.1 Unicode sanity code accept the full set of characters accepted by the 8.0 Unicode sanity code? If not we'll see a lot of problems like the one above. I believe this patch is the one causing the problem I see: http://www.mail-archive.com/pgsql-patches@postgresql.org/msg08198/unicode.di ff Is there any solution other than scrubbing the entire dataset to conform to the new (8.1) encoding rules? ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [BUGS] BUG #1989: Curious blob problem
On Sun, Oct 23, 2005 at 11:33:35AM +0100, Petr wrote: > I'm trying to use blob fields (bytea) and have a curious problem with it (in > Delphi). When i'm store the blob stream into DB, the length is 810 bytes. > When i'm trying to get data from DB, gives me only 807 bytes. I was try to > store entire streams into files and locate differences. Three bytes aren't > be in exported file in the middle of the file :-O. Have you done any tests that don't involve Delphi? With psql, for example? This might not be a PostgreSQL problem. > Can you look at this problem (i can send you these files). A test case would be useful: all SQL statements, data, and other steps that somebody could use to duplicate what you're doing. -- Michael Fuhr ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [BUGS] BUG #1987: UTF8 encoding differences hamper upgrades
Paul, To fix your dump so it will import, run: iconv -c -f UTF8 -t UTF8 -o fixed.sql dump.sql Kind Regards, John Hansen > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Paul Lindner > Sent: Sunday, October 23, 2005 1:34 AM > To: pgsql-bugs@postgresql.org > Subject: [BUGS] BUG #1987: UTF8 encoding differences hamper upgrades > > > The following bug has been logged online: > > Bug reference: 1987 > Logged by: Paul Lindner > Email address: [EMAIL PROTECTED] > PostgreSQL version: 8.1beta3 > Operating system: Fedora Core 4 x86_64 > Description:UTF8 encoding differences hamper upgrades > Details: > > I've been doing some test imports of UNICODE databases into > Postgres > > > > 8.1beta3. The only problem I've seen is that some data from > 8.0 > > > > databases will not import. > > > > > > > > > > I've generated dumps using pg_dump from 8.0 and 8.1. > Attempting to > > > > restore these results in > > > > > > > > > > Invalid UNICODE byte sequence detected near byte ... > > > > > > > > > > Question: > > > > > > > > > > Does the 8.1 Unicode sanity code accept the full set of > characters > > > > accepted by the 8.0 Unicode sanity code? > > > > > > > > > > If not we'll see a lot of problems like the one above. > > > > > > > > > > > > > > > I believe this patch is the one causing the problem I see: > > > > > > > > > > > http://www.mail-archive.com/pgsql-patches@postgresql.org/msg08 198/unicode.di > ff > > > > > > > > > > > > > Is there any solution other than scrubbing the entire dataset > to > > > > conform to the new (8.1) encoding rules? > > ---(end of > broadcast)--- > TIP 5: don't forget to increase your free space map settings > > --
Re: [BUGS] BUG #1988: keygen not implemented
Mike Clements wrote: Insert a row into the table using: Connection.prepareStatement(sql, Statement.RETURN_GENERATED_KEYS); The driver throws an exception saying this method is not yet implemented. This is an optional part of the JDBC spec, and the driver doesn't claim to support it in the metadata it provides (DatabaseMetaData.supportsGetGeneratedKeys() returns false). What it should do is create the prepared statement so when you execute it, the returned ResultSet has the generated primary key. Unfortunately this requires functionality in the backend that does not yet exist (support for "INSERT .. RETURNING ...", or similar). -O ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [BUGS] BUG #1985: cannot insert Chinese character into a table encoded with UTF8
""Jeff Tong"" <[EMAIL PROTECTED]> wrote > > The following bug has been logged online: > > Bug reference: 1985 > Logged by: Jeff Tong > Email address: [EMAIL PROTECTED] > PostgreSQL version: 8.1beta3 > Operating system: Windows XP > Description:cannot insert Chinese character into a table encoded > with UTF8 > Details: > > I am a traditional Chinese user in Hong Kong. 8.1beta3 for WinXP still > cannot let me insert Chinese character into a table encoded with UTF8. I > think it is very importance issue with CJK users who need Unicode encoded > tables. > > Here is a screenshot I took from command prompt: > http://www.tong.cc/pgsql8.1beta3.png > This is not a bug and it is answered several times before. It is the incorrect setting of client_encoding. Just iterate the solution here: test#\encoding LATIN_1 Then it works. Regards, Qingqing ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
