Closed (won't fix)
Project:
Drupal core
Version:
6.x-dev
Component:
database system
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
16 Oct 2007 at 14:20 UTC
Updated:
29 Oct 2008 at 12:33 UTC
Jump to comment: Most recent file
This is a split version of previous patch: http://drupal.org/node/178555. This patch only consider about the tidy up of database.pgsql.inc, plus minor update to db_table_exists() and db_column_exists(), which synchronize with mysql version. No change to db_query_range() and db_query_temporary() as that will consider as another issue. Should be trivial to commit.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | database.pgsql-inc-0.5.patch | 10.61 KB | hswong3i |
| #5 | drupal-6.x-dev-database_pgsql-0.4.patch | 4.37 KB | hswong3i |
| #3 | drupal-6.x-dev-database_pgsql-0.3.patch | 4.41 KB | hswong3i |
| #2 | drupal-6.x-dev-database_pgsql-0.2.patch | 4.41 KB | hswong3i |
| drupal-6.x-dev-database_pgsql-0.1.patch | 4.26 KB | hswong3i |
Comments
Comment #1
hswong3i commentedPatch tested for PostgreSQL 8.1.9 on Debian etch 4.0r1 with PHP 5.2.0-8+etch7. Both core and modules installation are passed with no error message. Should be trivial to commit.
Comment #2
hswong3i commentedPatch reroll via latest CVS HEAD. It is simple enough, with no critical logic change, and ready for commit. May someone give me a hand?
Comment #3
hswong3i commentedPatch reroll via latest CVS HEAD. Already merge with #172541 for D7 preparation, so shouldn't be too hurry right now.
Comment #4
klando commentedI'd like to prevent you to use COUNT for test if a row exist or not. In fact , it will be an extra cost in postgresl, you can just "select 1 from ....." wich is better.
Comment #5
hswong3i commented@klando: thank you for your suggestion :)
Patch reroll via CVS HEAD, with "SELECT 1" instead of "SELECT COUNT(...)".
I test this patch with a flesh new CVS HEAD PgSQL install, active PHP filter, and create a node with PHP filter which call db_table_exists() and db_column_exists() directly. The result is positive: they are working correctly as expected :)
Comment #6
hswong3i commentedNothing will happened even without this cleanup. Don't waste time in here.
Comment #7
hswong3i commented<code>is not allow for _db_error_page().Comment #8
hswong3i commentedLet's move focus to D7.