Re: pgAdmin 1.14 bug

On Fri, Dec 9, 2011 at 1:50 AM, Guillaume Lelarge <guillaume(at)lelarge(dot)info>wrote:

> On Thu, 2011-12-08 at 13:09 +0200, Julius Tuskenis wrote:
> > On 2011.12.08 12:37, Dave Page wrote:
> > > Hi
> > >
> > > On Thu, Dec 8, 2011 at 3:37 PM, Vjacheslav Vjacheslav
> > > <eferalgan(at)gmail(dot)com> wrote:
> > >> Hello,
> > >>
> > >> pgAdmin version: Version 1.14.0 (Sep 12 2011, rev: REL-1_14_0)
> > >> OS: Windows XP Pro RUS SP3
> > >> PostgreSQL: 9.1.1. (compiled without any options)
> > >>
> > >> bug description:
> > >> create a table (creation SQL below), then right click on it, and
> select
> > >> 'Properties', then write some comment and click Ok, and you receive
> an error
> > >> (see in attachment). Bug is beacasue of long contraint
> 'ck_pos_documents_1'.
> > >>
> > >> Table creation SQL:
> > > It works fine for me. Can anyone else reproduce the issue?
> > >
> > I can confirm the problem.
> >
> > WinXP SP3, pgAdmin 1.14.0, PostgreSQL 8.3.4 on i686-pc-linux-gnu,
> > compiled by GCC gcc (Gentoo 4.3.2-r3 p1.6, pie-10.1.5) 4.3.2
> >
> > What I noticed is the check constraint is beeing updated even if nothing
> > was done to it. I only added a comment ant thats the SQL that was
> generated:
> >
> > ALTER TABLE pos_documents DROP CONSTRAINT ck_pos_documents_1;
> > ALTER TABLE pos_documents ADD CONSTRAINT ck_pos_documents_1 CHECK
> > entry_type::text = 'Z-report open'::text OR entry_type::text =
> > 'Return'::text OR entry_type::text = 'Inkasso'::text OR entry_type::text
> > = 'Sale'::text OR entry_type::text = 'X-report'::text OR
> > entry_type::text = 'Cash Withdrawal'::text OR entry_type::text =
> > 'Z-report closed'::text OR entry_type::text = 'Open drawer'::text OR
> > entry_type::text = 'Service'::text OR entry_type::text = 'Z-report
> > Z1'::text OR entry_type::text = 'Z-report Z2'::text OR entry_type::text
> > = 'Z-report Z3'::text OR entry_type::text = ';
> > COMMENT ON TABLE pos_documents
> > IS 'test';
> >
> > You can see that the constraint text got truncated and left quotes open.
> >
>
> Works fine for me. Dave also. I guess we both use 1.14.1, and you both
> use 1.14.0. Update to 1.14.1 might fix your issue.
>
> Actually, that reminds me that we, once again, forgot to spread the
> news... will do.
>

I've updated pgadmin to version 1.4.1 (using upgrade.bat), but the problem
the same.