Richard Broersma Jr (rabro...@yahoo.com)

" ... might slow down ..." I guess they didn't check to know one way or ther other whether It does slow down a web page. The real answer depends upon your they kind of uses you have.

> * BSD license issues: Since PostgreSql comes under the
> Berkeley license scheme, this is again considered to be too open.

What does "too open" mean?  Is too open a bad thing?

> * Availability of inferior Data Storage mechanism:
> PostgreSql uses Postgres storage system, which is not considered to be transaction sae during PostgreSql hosting.

It seems they misspelled "safe". But in either case they also seemed to have confused MySQL with PostgreSQL on this point. Being transactionally "safe" is one of PostgreSQL's strongest points.

> * Its not far-flung: While MySql hosting and MSSql hosting have deeply
> penetrated into the market, PostgreSql hosting still remains to be passive in the database hosting market.

My gut says that this is probably true. But there are very good hosting sites that provide PostgreSQL.


> * Non-availability of required assistance for PostgreSQL hosting: Assistance is being provided via mailing lists. However there is no guarantee that the issue faced during PostgreSQL hosting would be resolved.

If you have a highly critical application that requires guaranteed assistance you are more than able to purchase it from some top notch consultant companies that support PostgreSQL. Just check out the PostgreSQL home page. So I don't this this point is correct either.

If you don't get too much feed back on this subject, just remember that topics like this come up frequently to the point of list member exhaustion. You can find such discussions if you search the list archive.

Regards,
Richard Broersma Jr.

--- On Tue, 1/29/08, Ivan Sergio Borgonovo <mail@webthatworks.it> wrote:

>> other than defining a function such that I can write:

   SELECT ( a-b ) as pippo
     FROM Yourtable
    WHERE ( a-b ) = 7
UNION ALL
   SELECT ( a*b ) as pippo
     FROM Yourtable
    WHERE ( a*b ) < 12
      AND a > 3
UNION ALL
   SELECT ( a+b ) as pippo
     FROM Yourtable
    WHERE ( a+b ) < 12
      AND a < 3;

--- On Tue, 1/22/08, Adam Rich <adam.r@sbcglobal.net> wrote:

> Is there a way to alter the
> existing keys? (it didn't jump out at me in the manual)

    ALTER TABLE your_table
DROP CONSTRAINT your_column_fkey_constraint,
ADD CONSTRAINT your_column_fkey_constraint
    FOREIGN KEY your_column
     REFERENCES parent_table( primary_column )
      ON UPDATE CASCADE;

Regards,
Richard Broersma Jr.

Actually, I think if you notice the example I posted previously, I made both the Unique ID column and object type column a composite primary key.

The other tables referenced this composite primary key as foreign keys using referential integrity ON UPDATE CASCADE. This means that they database ~would~ maintain/enforce the object-type portion of the foreign key automatically for you.

Regards,
Richard Broersma Jr.

Maybe a Freudian slip? ;)