[wp-hackers] PostgreSQL port status?
robin.adr at gmail.com
Thu Oct 4 03:59:02 GMT 2007
True, but it's always better to be safe than sorry (as much as I agree with
you). Also, at least in my opinion, it makes the SQL more readable --
keywords are in caps, strings surrounded by straight single quotes, and
DB/table/field names wrapped in backticks.
On 10/3/07, Computer Guru <computerguru at neosmart.net> wrote:
> IMO it's highly unlikely MySQL would ever add a keyword that's in use as a
> table name in the more popular open source platforms.... After all, we're
> all on the same team here :)
> On 10/4/07, Tom Barta <tbarta at gmail.com> wrote:
> > On 10/2/07, Leonid Mamchenkov <leonid at mamchenkov.net> wrote:
> > > On 10/2/07, usleepless at gmail.com <usleepless at gmail.com> wrote:
> > > > But as Tom pointed out, (reserverd) keywords are ... well ... kind
> > > > reserved. Don't use them as identifiers.
> > >
> > > I guess there is an added benefit of forward compatibility in escaping
> > > fields and table names. Words which are not reserved now can become
> > > so in the future.
> > Ok, so there's at least two options:
> > 1) Use backticks to escape tables and fields. This future-proofs
> > against MySQL reserved keyword changes (how frequently does that
> > happen?). It also makes it harder to use /any other database/ with
> > Wordpress.
> > 2) Use non-reserved tables and fields. If a new version of MySQL
> > comes out that adds an inconvenient reserved word, then the first
> > version of WP needs to add backticks or provide a DB upgrade path with
> > a field rename.
> > How frequently is a new version of MySQL expected to add keywords that
> > collide with the WP schema? It seems to me like this is something
> > that deliberately hurts any future for cross-platform WP support
> > (which is an issue that comes up frequently, so it is a real issue for
> > some people) to avoid a slim chance that some future version of MySQL
> > will change things. Just because WP is only targetted towards MySQL
> > doesn't mean that it should go out of its way to entrench itself in
> > MySQL for (what I view as) a questionable benefit.
> > --
> > Tom
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> Computer Guru
> NeoSmart Technologies
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers