Re: multibyte regression tests
От | Andrew Dunstan |
---|---|
Тема | Re: multibyte regression tests |
Дата | |
Msg-id | 42D83290.1070002@dunslane.net обсуждение исходный текст |
Ответ на | Re: multibyte regression tests ("Ayush Parashar" <aparashar@greenplum.com>) |
Список | pgsql-hackers |
I am totally confused by your response and Luke's. I think we might be talking completely at cross purposes. My original question had nothing to do with the COPY patch. cheers andrew Ayush Parashar wrote: >Andrew, Luke, > >As pointed by Luke, the reason for using mb regression suite (src/test/mb), >is to consolidate all similar kinds of multi-byte/client encoding tests at >one place. > >Thanks, >Ayush > >On 7/15/05 1:36 PM, "Luke Lonergan" <llonergan@greenplum.com> wrote: > > > >>Andrew, >> >> >> >>>Good. So should we roll this up into the standard regression suite? Why >>>are these tests separate? Is it just that they need a UTF8 encoded db >>>rather than an SQL-ASCII encoded db? >>> >>> >>I think that was the idea - the src/test/mb kit was already there and was >>designed to create the UTF8 database and controlled circumstances for a >>conversion test, so we used it for the similar testing for COPY. >> >>It could possibly be moved into the "make check" regression suite, if the >>regression DB is always created with UTF8. >> >>Ayush may be able to add to this. >> >>- Luke >> >> >> > > > >---------------------------(end of broadcast)--------------------------- >TIP 3: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faq > > >
В списке pgsql-hackers по дате отправления: