[wp-hackers] Google SoC: PostgreSQL port

[Computer Guru]

I'm just worried about the Plugins... because as others noted, most will access the DB directly without using the API.

However, you could just remove external access to the DB, I guess that would force them to use the API...

You guys might want to take a look at IPB, I haven't seen it for myself, but from what I know, it's just one php file they call a database "driver" that needs replacing..

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
> Sent: Friday, March 23, 2007 8:20 AM
> To: wp-hackers at lists.automattic.com
> Subject: Re: [wp-hackers] Google SoC: PostgreSQL port
> 
> 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...
> 
> --Matt
> 
> 
> On 3/22/07, Computer Guru <computerguru at neosmart.net> wrote:
> >
> > Matt, there was this plugin I came across for WP 1.5, and it sounds
> > interesting.
> > Instead of rewriting db.php, this plugin instead uses PREG to replace
> > queries on the fly.....
> >
> > *searches for link*
> >
> > http://elizabethmariesmith.com/?p=19
> >
> > Her plugin is decent, I downloaded a copy of WP 1.5.2 and it had some
> > glitches, but it WORKED....
> >
> > Do you have any idea if this kind of system COULD be implemented via
> a
> > plugin for WP 2.1.x?
> >
> > Technically, this would address ALL the issues raised regarding
> plugin
> > DB-access structure, non-ANSI functions, etc.....
> >
> > 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
> > > Sent: Friday, March 23, 2007 7:49 AM
> > > To: wp-hackers at lists.automattic.com
> > > Subject: Re: [wp-hackers] Google SoC: PostgreSQL port
> > >
> > > A better project would be to make WP be multi-database compatible.
> > > Maybe
> > > even make it more extendable so other people would be able to make
> > > there own
> > > DB ports be simply making up a file. I'm sure you could use classes
> and
> > > functions to produce this (such as, make a function called
> db_insert(),
> > > and
> > > then in a file go:
> > >
> > > function db_insert(stuff) {
> > > //database query stuff here for inserting data
> > > }
> > >
> > > and then others. Then, make an option for which DB you want to use
> in
> > > wp-config.php and make a folder where the files for the different
> DBs
> > > would
> > > go to in like wp-includes/db [or something])...
> > >
> > >
> > > On 3/22/07, David Chait <davebytes at comcast.net> wrote:
> > > >
> > > > There's a fellow (dave cramer) who has an email address at
> > > > postgresintl.com who announced a port about 10 days back...
> Before
> > > > looking at it for SoC, well worth knowing whether there's
> actually a
> > > big
> > > > enough project left, etc.
> > > >
> > > > -d
> > > >
> > > > Olexandr Melnyk wrote:
> > > > > Hello,
> > > > >
> > > > > today I was browsing through the list of mentoring
> organisations,
> > > > > participating in Google Summer of Code, and luckily found
> WordPress
> > > > > there.
> > > > > And then I reminded myself an idea I have thought of some time
> ago:
> > > to
> > > > > develop PostgreSQL port of WordPress. I would like to hear some
> > > opinions
> > > > > from the community: what do you think of this idea?
> > > > >
> > > > > I have read some discussions on this mailing list on this
> topic,
> > > and
> > > > > found
> > > > > that I am not the only person interested in the port, and that
> > > there are
> > > > > already intensions being made towards multi-database support
> both
> > > in
> > > > > default
> > > > > WordPress (removing enums from database, etc) and fork
> projects.
> > > > >
> > > > > I already have a rough list of things to be done, and would
> gladly
> > > > > discuss
> > > > > it if there's anyone interested.
> > > >
> > > > _______________________________________________
> > > > 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
> >
> > _______________________________________________
> > 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