Closed (fixed)
Project:
Taxonomy Access Control
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
24 Feb 2005 at 23:26 UTC
Updated:
7 Apr 2005 at 19:15 UTC
Jump to comment: Most recent file
This patch allows taxonomy_access to work with PostgreSQL while (hopefully!) preserving MySQL compatibility.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | taxonomy_access_cvs-pgsql.patch | 7.38 KB | Zed Pobre |
| ta_pgsql.diff | 6.31 KB | elonen |
Comments
Comment #1
pyromanfo commentedIs this against 4.5.0 or CVS? I'm just making sure because I thought I got rid of that "WHERE 1" stuff a while ago. That said, thanks for the patch. If it's against CVS I'll go ahead and commit it.
Comment #2
elonen commentedIt's against 4.5. Aside from removing the "WHERE 1" conditions, the other change was just to substitute MySQL REPLACE statements with DELETE/INSERT pairs.
Comment #3
Zed Pobre commentedJust for your information, there are still WHERE 1 lines still in the CVS version. I just checked. I'm in the process of trying to repeat this patch by hand against the CVS tarball.
Comment #4
Zed Pobre commentedI am attaching an updated patch against the CVS version of the module. This covers the module alone, not the SQL required to set up the tables.
Comment #5
pyromanfo commentedOkay, I commited it to CVS, you also missed one of the "REPLACE INTOs" you added the "DELETE" but didn't change it to "INSERT". I fixed that. Though having to change the update functions to "INSERT" instead of "REPLACE" hopefully doesn't cause more bugs, but I'll just have to fix it another way if it comes to that.
Comment #6
(not verified) commented