From: Thomas Kellerer <spam_eater@gmx.net>
To: pgsql-sql@postgresql.org
Subject: Re: Finding Max Value in a Row
Date: Fri, 11 May 2012 22:05:24 +0200
Message-ID: <jojrc9$uof$2@dough.gmane.org> (raw)
In-Reply-To: <CAAQLLO6whu1np_oiMze-EUDL_3a5WSmrM+mqytQuhM40wOB_Fg@mail.gmail.com>
References: <CAAQLLO6EhUi0OUi38BiH+qmgKqY+mY27_hGBQJiC5rbWorXQbw@mail.gmail.com>
<00ee01cd2fab$1b528b80$51f7a280$@yahoo.com>
<CAAQLLO7-O26xpisutPoud__iDaco6WtZCr6CBG5OgiwpgvWd6g@mail.gmail.com>
<4FAD6BFE.3090905@gmail.com>
<CAAQLLO6whu1np_oiMze-EUDL_3a5WSmrM+mqytQuhM40wOB_Fg@mail.gmail.com>
Carlos Mennens wrote on 11.05.2012 21:53:
> Very good question and asked by myself to the original SQL author and
> he explained while he didn't use the most efficient data types, he
> used ones "he" felt would be more transparent across a multitude of
> RDBMS vendors. So the answer is no, it would not be an issue
> considering I use and will always use PostgreSQL. If someone else uses
> a different vendor, they can manage that import/export process then.
You should tell those people that char is a bad choice in _any_ DBMS due to the padding that is involved.
varchar would have been slightly better.
But it's never, ever a good idea to store numbers in a character column.
*Every* RDBMS has some kind of integer datatype (they might just have different names).
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: spam_eater@gmx.net
Subject: Re: Finding Max Value in a Row
In-Reply-To: <jojrc9$uof$2@dough.gmane.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox