Hi,
-- *Harshal Dhumal* *Software Engineer* EnterpriseDB India: http://www.enterprisedb.com The Enterprise PostgreSQL Company On Wed, Feb 22, 2017 at 3:29 PM, Dave Page <dp...@pgadmin.org> wrote: > Harshal, can you look into these issues please? > > Thanks. > > On Tue, Feb 21, 2017 at 10:38 PM, Nigel Tucker < > ni...@specialisedstructures.co.nz> wrote: > >> Hi Dave, >> >> >> >> As if you don’t have enough issues, I have two minor problems with the >> Windows release. >> >> >> >> If I view all rows in a table, and then add a new row at the bottom of >> that table, any double precision columns will only set the field to an >> integer, all values to the right of the decimal point are lost. SQL Updates >> to the same field work just fine. >> >> >> > This is fixed in this commit <https://git.postgresql.org/gitweb/?p=pgadmin4.git;a=commitdiff;h=88cae263b2e35954bc3a5358b85c279d4b891818> and will be available in next release of pgAdmin4. Secondly, while adding a new row, any Boolean column cannot be set to >> false. The app runs through the options, showing a false box, but selecting >> that restores the value of the field to Null. If you select the True >> option, that’s fine and then you can go back to it and eventually select >> the false option after four or five other options – and that works fine. >> >> >> > I have logged issue (#RM2218) <https://redmine.postgresql.org/issues/2218> for boolean editor. > Just a couple of minor issues in an otherwise robust product, >> >> >> >> Thanks >> >> >> >> Nigel >> >> >> >> *Dr Nigel Tucker* >> >> System Architect >> >> Specialised Structures NZ >> >> Telephone Direct (NZ) +64 (0) 3 482 2473 <+64%203-482%202473> >> >> >> >> [image: SS with Custom] >> >> >> > > > > -- > Dave Page > Blog: http://pgsnake.blogspot.com > Twitter: @pgsnake > > EnterpriseDB UK: http://www.enterprisedb.com > The Enterprise PostgreSQL Company >
