Thread: invalid data for encoding
I have just noticed that we are still accepting data that is invalid for the server encoding, and in consequence we can produce a dump which we can't subsequently load. This is a major bug IMNSHO, and needs to be fixed for 8.3. Mark, have you made any progress on fixing this? The last mention on list I can see from you is April 17th. cheers andrew
On Thu, 2007-08-23 at 17:04 -0400, Andrew Dunstan wrote: > I have just noticed that we are still accepting data that is invalid for > the server encoding, and in consequence we can produce a dump which we > can't subsequently load. This is a major bug IMNSHO, and needs to be > fixed for 8.3. I agree. Links to previous discussion: http://archives.postgresql.org/pgsql-bugs/2006-10/msg00246.php http://archives.postgresql.org/pgsql-bugs/2006-11/msg00000.php http://archives.postgresql.org/pgsql-bugs/2006-11/msg00033.php I understand there are backwards compatibility issues that we should consider, and we should consider them carefully. However, I don't think that the current behavior is correct, for the same reason that I don't think that "February 31st, 2007" should be allowed in a date column. Regards,Jeff Davis