Thread: pgAdmin 1.0-beta2 numeric(12,3) displayed as numeric(...,2) in View Data filtered
pgAdmin 1.0-beta2 numeric(12,3) displayed as numeric(...,2) in View Data filtered
From
"Temp key: basic, via spamcop"
Date:
The subject pretty much says it all. Screen shot snippets enclosed for those who work better visually. The amounts with value at the third decimal digit (i.e., milliDollars), were displayed rounded, not truncated, at 2 places. Context: System running pgAdmin: Mac OS X El Capitan 10.11.5 SQL Server: PostgreSQL 9.4.5 on x86_64-apple-darwin, compiled by i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00), 64-bit Regards Gavan Schneider
Attachment
Re: pgAdmin 1.0-beta2 numeric(12,3) displayed as numeric(...,2) in View Data filtered
From
"Temp key: basic, via spamcop"
Date:
On 7/17/16 at 5:52 PM, Gavan Schneider wrote: And yes I did mean to say the application itself is called pgAdmin 4 >The subject pretty much says it all. Screen shot snippets enclosed for >those who work better visually. The amounts with value at the third >decimal digit (i.e., milliDollars), were displayed rounded, not >truncated, at 2 places. > >Context: >System running pgAdmin: Mac OS X El Capitan 10.11.5 SQL Server: >PostgreSQL 9.4.5 on x86_64-apple-darwin, compiled by >i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. >build 5658) (LLVM build 2336.11.00), 64-bit > >Regards >Gavan Schneider > >----- PS. Is it worth considering versioning this as "4.01.0-beta2" with the implication that any future pgAdmin 5 would start with version "5.01.0-alpha1" etc. ?
Re: pgAdmin 1.0-beta2 numeric(12,3) displayed as numeric(...,2) in View Data filtered
From
Melvin Davidson
Date:
<div style="color:#000; background-color:#fff; font-family:Courier New, courier, monaco, monospace, sans-serif;font-size:24px"><divid="yui_3_16_0_1_1468763337811_10784"><b><span id="yui_3_16_0_1_1468763337811_10783">I'm prettysure it would be more helpful if you provided:</span></b></div><div id="yui_3_16_0_1_1468763337811_10782"><b><spanid="yui_3_16_0_1_1468763337811_10781">A. The structure of the table(s) involved.</span></b></div><divid="yui_3_16_0_1_1468763337811_10780"><b><span id="yui_3_16_0_1_1468763337811_10779">B. Theactual query you used to retrieve the data.</span></b></div><div id="yui_3_16_0_1_1468763337811_10762"><b><span id="yui_3_16_0_1_1468763337811_10778">C.Did you run the query in PgAdmin Query Tool or psql ?</span></b></div><div id="yui_3_16_0_1_1468763337811_10739"> </div><divclass="signature" id="yui_3_16_0_1_1468763337811_10622"><div id="RTEContent"><fontsize="4"><span style="font-weight:bold;font-family:arial;color:rgb(0, 0, 255);">Melvin Davidson </span></font><br/><font id="yui_3_16_0_1_1468763337811_10698" size="3" style="font-weight:bold;"><span id="yui_3_16_0_1_1468763337811_10699"style="color:rgb(128, 0, 255);">I reserve the right to fantasize. Whether or not you</span><br style="color:rgb(128, 0, 255);" /><span id="yui_3_16_0_1_1468763337811_10697" style="color:rgb(128, 0, 255);">wishto share my fantasy is entirely up to you. </span><img data-id="d5427697-0482-c2c9-d5cd-0801f5061d2e" src="http://us.i1.yimg.com/us.yimg.com/i/mesg/tsmileys2/01.gif"style="color:rgb(128, 0, 255);" /></font><font id="yui_3_16_0_ym19_1_1467319472979_3360"size="3" style="font-weight:bold;"><br /></font><font id="yui_3_16_0_1_1468763337811_10696"size="3"><span id="yui_3_16_0_1_1468763337811_10695" style="font-weight:bold;font-family:courier;">FolkAlley - All Folk - 24 Hours a day </span><span style="font-weight:bold;font-family:courier;"><br/>www.folkalley.com<br /><br /></span></font></div></div><div class="qtdSeparateBR"id="yui_3_16_0_1_1468763337811_10688"><br /><br /></div><div class="yahoo_quoted" id="yui_3_16_0_1_1468763337811_10694"style="display: block;"><div id="yui_3_16_0_1_1468763337811_10693" style="font-family:Courier New, courier, monaco, monospace, sans-serif; font-size: 24px;"><div id="yui_3_16_0_1_1468763337811_10692"style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande,sans-serif; font-size: 16px;"><div dir="ltr" id="yui_3_16_0_1_1468763337811_10691"><font face="Arial" id="yui_3_16_0_1_1468763337811_10690"size="2"><hr id="yui_3_16_0_1_1468763337811_10689" size="1" /><b><span style="font-weight:bold;">From:</span></b>"Temp key: basic, via spamcop" <pgadmin-gts@snkmail.com><br /><b><span style="font-weight:bold;">To:</span></b> pgadmin-support@postgresql.org <br /><b><span style="font-weight: bold;">Sent:</span></b>Sunday, July 17, 2016 4:12 AM<br /><b><span style="font-weight: bold;">Subject:</span></b> Re: [pgadmin-support]pgAdmin 1.0-beta2 numeric(12,3) displayed as numeric(...,2) in View Data filtered<br /></font></div><divclass="y_msg_container" id="yui_3_16_0_1_1468763337811_11923"><br />On 7/17/16 at 5:52 PM, Gavan Schneiderwrote:<br clear="none" /><br clear="none" />And yes I did mean to say the application itself is called <br clear="none"/>pgAdmin 4<br clear="none" /><br clear="none" />>The subject pretty much says it all. Screen shot snippetsenclosed for<br clear="none" />>those who work better visually. The amounts with value at the third<br clear="none"/>>decimal digit (i.e., milliDollars), were displayed rounded, not<br clear="none" />>truncated, at 2 places.<brclear="none" />><br clear="none" />>Context:<br clear="none" />>System running pgAdmin: Mac OS X El Capitan10.11.5 SQL Server:<br clear="none" />>PostgreSQL 9.4.5 on x86_64-apple-darwin, compiled by<br clear="none" />>i686-apple-darwin11-llvm-gcc-4.2(GCC) 4.2.1 (Based on Apple Inc.<br clear="none" />>build 5658) (LLVM build 2336.11.00),64-bit<br clear="none" />><br clear="none" />>Regards<br clear="none" />>Gavan Schneider<br clear="none"/>><br clear="none" />>-----<br clear="none" /><br clear="none" />PS. Is it worth considering versioningthis as "4.01.0-beta2" <br clear="none" />with the implication that any future pgAdmin 5 would start with <br clear="none"/>version "5.01.0-alpha1" etc. ?<div class="yqt2632878572" id="yqtfd31468"><br clear="none" /><br clear="none"/><br clear="none" /><br clear="none" />-- <br clear="none" />Sent via pgadmin-support mailing list (<a href="mailto:pgadmin-support@postgresql.org"shape="rect" ymailto="mailto:pgadmin-support@postgresql.org">pgadmin-support@postgresql.org</a>)<brclear="none" />To make changes to yoursubscription:<br clear="none" /><a href="http://www.postgresql.org/mailpref/pgadmin-support" shape="rect" target="_blank">http://www.postgresql.org/mailpref/pgadmin-support</a></div><br/><br /></div></div></div></div></div>
Re: pgAdmin 1.0-beta2 numeric(12,3) displayed as numeric(...,2) in View Data filtered
From
"Temp key: basic, via spamcop"
Date:
On 7/17/16 at 11:57 PM, Melvin Davidson melvin6925-at-yahoo.com wrote:
>I'm pretty sure it would be more helpful if you provided:A. The
>structure of the table(s) involved.B. The actual query you used to
>retrieve the data.C. Did you run the query in PgAdmin Query Tool or
>psql ? Melvin Davidson I reserve the right to fantasize. Whether or
>not you wish to share my fantasy is entirely up to you.
No need for fantasy, so nothing to share.
I thought I was providing a simple report of a display bug in a
beta release product with sufficient evidence to prove there is
a problem and nothing more. I am trusting such bug reports are
welcome on this list. Otherwise please let me know where I
should be posting.
While I'm not sure how additional information would be helpful,
since no additional information changes the discrepancy between
the data type and its display, I am answering the questions:
The pgAdmin 4 screen shot snippet showed the "amount" column as
"numeric(12,3)" and the tabulated data below this header has
only two decimal places. The pgAdmin 4 query: SELECT * FROM accounts.transactions WHERE transaction_ref=1506
ORDER BY transaction_ref,transaction_line
The psql screen shot snippet showed the underlying data does
have some non-zero digits in the third decimal place. ANd psql
displays the data to thee decimal places as per data type definition. The psql query: SELECT * FROM
accounts.transactionsWHERE transaction_ref=1506;
The table definition: CREATE TABLE accounts.transactions ( tax_code character(1) COLLATE
"default".pg_catalogNOT NULL, transaction_ref integer NOT NULL, transaction_line integer NOT NULL,
account_itemchar_short_key COLLATE
"default".pg_catalog NOT NULL, amount numeric(12, 3), job char_short_key COLLATE "default".pg_catalog NOT
NULL DEFAULT 0, transaction_memo text COLLATE "default".pg_catalog
DEFAULT ''::text, alt_ledger character(6) COLLATE "default".pg_catalog, CONSTRAINT transactions_pkey
PRIMARYKEY
(transaction_line, transaction_ref), CONSTRAINT transactions_account_item_fkey FOREIGN KEY (account_item)
REFERENCES accounts.account_items (account_item)
MATCH SIMPLE ON UPDATE CASCADE ON DELETE RESTRICT, CONSTRAINT transactions_alt_ledger_fkey
FOREIGNKEY (alt_ledger) REFERENCES accounts.ledgers (ledger) MATCH SIMPLE ON UPDATE CASCADE
ON DELETE RESTRICT DEFERRABLE, CONSTRAINT transactions_job_fkey FOREIGN KEY (job)
REFERENCESaccounts.jobs (job) MATCH SIMPLE ON UPDATE CASCADE ON DELETE RESTRICT,
CONSTRAINTtransactions_ref_fkey FOREIGN KEY (transaction_ref) REFERENCES accounts.transaction_refs
(transaction_ref) MATCH SIMPLE ON UPDATE CASCADE ON DELETE NO ACTION DEFERRABLE
INITIALLYDEFERRED, CONSTRAINT transactions_tax_code_fkey FOREIGN KEY (tax_code) REFERENCES
accounts.taxcodes(tax_code) MATCH SIMPLE ON UPDATE CASCADE ON DELETE RESTRICT ) WITH (
OIDS = FALSE ) TABLESPACE pg_default;
Regards
Gavan Schneider