Thomas Zehetbauer wrote:
> Why do I have to use FOUR queries to accomplish the same result I can
> get from MySQL with only ONE query:
>
> alter table users add column $ColumnName text;
> alter table users alter column $ColumnName set default '';
> update users set t_shirt_size='' where $ColumnName is null;
> alter table users alter column $ColumnName set not null;
>
> MySQL is CLEARLY SUPERIOR in terms of
> - usability
> - see above
> - performance
> - uses index for for min()/max()
> - reliability
> - no need to use vacuum
> - no need to dump and restore databases for version upgrade
> - never screwed up any of my databases
>
> I would therefore urgently recommend that
> 1) development of postgresql shall be immediately ceased
> 2) any resources gained thereby (developers, mirrors) shall be donated
> to MySQL
> 3) code produced by the former postgresql developers shall be subject to
> a mandatory peer review before it is included in MySQL
Thomas,
you know about this problem for quite some time now:
http://www.faqchest.com/prgm/pgsql-l/pgsql-02/pgsql-0203/pgsql-020330/pgsql02031308_14224.html
I assume that you have some experience in database development and since
you know about this for so long, have some idea for us. Can you please
explain in some detail how to do this given the catalog based extensible
functionality of PostgreSQL.
How does MySQL achieve to use an index on a user defined data type where
a user defined max() aggregate was created for?
I know that MySQL is far superior. Unfortunately though some of my
applications use stored procedures, referential actions, updateable
views, triggers, subselects and other features that are not yet
supported by this excellent product. Please let me know when some of
these will be available and until then, just shut up!
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck@Yahoo.com #