Find out what version of mysql they're using. Recent versions include UNION
queries and allow table types that have (limited) support for transactions
and foreign key constraints; older versions don't.
MySQL can be run in ANSI-compliant mode, which fixes things like: SELECT foo
|| bar means concatenate foo + bar, rather than meaning foo OR bar, which is
the usual MySQL interpretation.
There's a document I wrote in techdocs about moving from mysql to pgsql.
Read it backwards.
Sorry to hear. PG is (IMHO) much nicer than mysql, especially if you take
advantage of its features like transactions, foreign keys, triggers, etc.,
which are missing or less featureful in mysql.
- J.
Joel BURTON | joel@joelburton.com | joelburton.com | aim: wjoelburton
Knowledge Management & Technology Consultant
> -----Original Message-----
> From: pgsql-general-owner@postgresql.org
> [mailto:pgsql-general-owner@postgresql.org]On Behalf Of
> pilsl@goldfisch.at
> Sent: Monday, May 06, 2002 5:45 PM
> To: pgsql-general@postgresql.org
> Subject: [GENERAL] help with *mysql*
>
>
> my nightmare is coming true: I need to port a whole CMS from postgres
> to mysql. I just started taking the first looks on mysql and all
> seems so wrong ;)
>
> it doesnt have system-unique OID's, it doesnt have something like
> offset, it doesnt accept my ROLLBACK.
>
> but: I will have to learn how to move around all this things, so what
> I want to ask here is, if someone knows some docs about all these
> things a programmer will have to face if switching from postgres to
> mysql.
>
>
> and the reason for all this is, that all this cheep providers offer
> mysql and all customers think, hey : this provider is 100USD less per
> month and offer 100.000 emailaliases. I tried to mention "transaction"
> and "sql-standard" but they only stared at me ...
>
>
> thnx,
> peter
>
> ps: sorry for this whiny-posting
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
