Tweet
Okay, after having converted my work's Content Management System (that I wrote myself earlier in MySQL) to Postgres, I've started thinking about vB3 on Postgres.
Having a fairly good grasp of the vB3 codebase, its object & functions & engine, I think a vB3 on Postgres would require quite a thorough rewrite. Simply updating the db_mysql.php file with a db_pgsql.php version that is Postgres-compatible won't work, for starters. PHP and Postgres work in various ways that are completely incompatible with PHP/MySQL, and some functions/methods that vB currently uses simply cannot be done in Postgres without altering other .php files too. I'm not even getting started on what vB can do with Postgres that it currently cannot, of course...
So anyway, to get to the point of this thread: I'm curious, and my curiosity is aimed first and foremost to Jelsoft; what are Jelsoft's plans on vB3-on-Postgres, and if there are any, how is this going to be dealt with?
Will there be a vB3-PE, a "vBulletin 3, Postgres Edition" so to speak, that users with a current vB3 can upgrade to via another complicated and extensive upgrade script? Or will it be a separate, mysql-version-incompatible product because so much code will/should be rewritten?
The database layout on such a version should, imho, be changed quite radically. Just running off of Postgres is one thing, but I would say, if you're going to make a Postgres version, do it the right way: make use of Postgres' features to the fullest extent. Problem with that is that many things in vB3 will simply not work the same way anymore, so what are Jelsoft's thoughts on that?
And also, what does the community think of all this? Myself, I would absolutely love a Postgres 7.4-compatible vBulletin 3. There are just so many things that Postgres can automate for vBulletin, and on the whole, such a version would be fantastic for larger boards (any board with more than 1 million posts could effectively run 2-3 times as fast on Postgres, if not faster). On top of that, Postgres allows for far more advanced indexing (esp. as of 7.4, where you can make indexes using generic expressions as opposed to column/function only) which can open up a whole new dimension to how vBulletin works and functions.
All in all, I can only say that working with Postgres so far has been an absolute bliss, much nicer and faster than MySQL, and so much more powerful. A vBulletin 3 based on Postgres, making use of its features as much as possible, would be utter heaven. But, that's just my opinion. I'd like to know Jelsoft's and the community's opinion on this.
Having a fairly good grasp of the vB3 codebase, its object & functions & engine, I think a vB3 on Postgres would require quite a thorough rewrite. Simply updating the db_mysql.php file with a db_pgsql.php version that is Postgres-compatible won't work, for starters. PHP and Postgres work in various ways that are completely incompatible with PHP/MySQL, and some functions/methods that vB currently uses simply cannot be done in Postgres without altering other .php files too. I'm not even getting started on what vB can do with Postgres that it currently cannot, of course...
So anyway, to get to the point of this thread: I'm curious, and my curiosity is aimed first and foremost to Jelsoft; what are Jelsoft's plans on vB3-on-Postgres, and if there are any, how is this going to be dealt with?
Will there be a vB3-PE, a "vBulletin 3, Postgres Edition" so to speak, that users with a current vB3 can upgrade to via another complicated and extensive upgrade script? Or will it be a separate, mysql-version-incompatible product because so much code will/should be rewritten?
The database layout on such a version should, imho, be changed quite radically. Just running off of Postgres is one thing, but I would say, if you're going to make a Postgres version, do it the right way: make use of Postgres' features to the fullest extent. Problem with that is that many things in vB3 will simply not work the same way anymore, so what are Jelsoft's thoughts on that?
And also, what does the community think of all this? Myself, I would absolutely love a Postgres 7.4-compatible vBulletin 3. There are just so many things that Postgres can automate for vBulletin, and on the whole, such a version would be fantastic for larger boards (any board with more than 1 million posts could effectively run 2-3 times as fast on Postgres, if not faster). On top of that, Postgres allows for far more advanced indexing (esp. as of 7.4, where you can make indexes using generic expressions as opposed to column/function only) which can open up a whole new dimension to how vBulletin works and functions.
All in all, I can only say that working with Postgres so far has been an absolute bliss, much nicer and faster than MySQL, and so much more powerful. A vBulletin 3 based on Postgres, making use of its features as much as possible, would be utter heaven. But, that's just my opinion. I'd like to know Jelsoft's and the community's opinion on this.
Comment