[wp-hackers] PostgreSQL port status?

[Robin Adrianse]

More specifically, WordPress isn't aiming whatsoever to be compatible with
database engines other than MySQL -- if you want to run it on something
else, then it's up to you to figure out what to do about the MySQL-specific
SQL.

On 9/30/07, Matt <speedboxer at gmail.com> wrote:
>
> No particular post in particular, just saying.
>
> I see your point, but it doesn't seem like (in my opinion) it should be
> WordPress' job to make it so that other databases can be used. Forking
> WordPress is the best option, if you want to use a different database than
> WordPress was made for, in my opinion...
>
>
> On 9/30/07, usleepless at gmail.com <usleepless at gmail.com> wrote:
> >
> > Matt,
> >
> > On 10/1/07, Matt <speedboxer at gmail.com> wrote:
> > > Since MySQL is the required database for WordPress, I think we might
> as
> > well
> > > take advantage of MySQL-specific features, and not try to make it all
> > > "generic". If we're going to only support 1 database, we should take
> > > advantage of that.
> > >
> > > I'm not saying this just to make using other databases harder, either.
> > I'm
> > > saying it because WordPress has already decided to use just MySQL, and
> > > that's what you should be running it on...
> >
> > first of all, i have no idea which post/comment you are replying,
> > since there is no quoted text ( context ) in your message.
> >
> > but assuming you are referring to my latest post: i am not sure what
> > you mean about mysql-specific "features". i don't consider accepting
> > "`" in a query statement a feature. i don't consider writing LIMIT x,y
> > instead of LIMIT y OFFSET x a feature. i don't consider adding
> > "IGNORE" to an insert-statement a feature. that is just a hack.
> >
> > if you are talking about the FOUND/CALC-ROWS "feature", you might have
> > a point. but since a statement with this feature takes longer to
> > execute than a statement without this feature, i suspect it is just a
> > dialect issue as well. i might be wrong about this.
> >
> > but my post was certainly not about features. creating indices in the
> > create-table statement is more vendor-specific than
> > CREATE INDEX indexname ON tablename(fieldname[,fieldname]*);
> >
> > which works on any RDMBS.
> >
> > it is about complying to standards instead of complying to vendors.
> >
> > there is no specific advantage WP is currently taking advantage of
> > MySQL, apart from it's availability.
> >
> > different RDMBS systems have different strengths: MySQL may be fast
> > and free, PGSQL is robust and free ( and just as fast ), MSSQL is
> > readily available in the windows world, Oracle .... yadayadayada.
> >
> > regards,
> >
> > usleep
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> >
>
>
>
> --
> Matt (speedboxer at gmail.com)
> http://mattsblog.ca/
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>