[wp-hackers] Google SoC: PostgreSQL port
Computer Guru
computerguru at neosmart.net
Fri Mar 23 18:17:15 GMT 2007
That's what I was thinking..
This would be a minimally-invasive and rather compatible method of pulling it off, esp. if we're looking to not mess up tens of thousands of plugins and bite off more than we can chew.
The only concern is that PREG is naturally a _regular_ expression tool, I'm not sure if SQL queries are actually to be considered "regular" or not.
However, even if PREG is out of the question, you can still easily (and lightly) create a balanced parser, though that would be several hundred times easier in another language :P
Computer Guru
NeoSmart Technologies
http://neosmart.net/blog/
> -----Original Message-----
> From: wp-hackers-bounces at lists.automattic.com [mailto:wp-hackers-
> bounces at lists.automattic.com] On Behalf Of Matt Mullenweg
> Sent: Friday, March 23, 2007 8:07 PM
> To: wp-hackers at lists.automattic.com
> Subject: Re: [wp-hackers] Google SoC: PostgreSQL port
>
> Matt wrote:
> > Doing a replace of the queries on the fly wouldn't be preferable. It
> would
> > be laggy and slow down the page loading time. I like the way I
> mentioned,
> > that way people can just go and make a file with different functions
> in it
> > and then put the appropriate DB queries inside the functions. Maybe
> there's
> > another way of doing it though...
>
> We do thousands of preg operations on every page load. There are going
> to be 10-30 queries on a page, so 10-30 pregs isn't going to make any
> perceptible difference.
>
> --
> Matt Mullenweg
> http://photomatt.net | http://wordpress.org
> http://automattic.com | http://akismet.com
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
More information about the wp-hackers
mailing list