Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.it's a little code factorisation because i found some redundant parts.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | database_all.patch | 10.41 KB | gilcot |
| #3 | database.pgsql.patch.txt | 1.33 KB | gilcot |
| #2 | database.mysqli.patch.txt | 1.32 KB | gilcot |
| #1 | database.mysql.patch_0.txt | 1.32 KB | gilcot |
| database.patch_0.txt | 1.57 KB | gilcot |
Comments
Comment #1
gilcot commentedthe rewrite impactes sub-componants : here is mysql ones
Comment #2
gilcot commentedthe rewrite impactes sub-componants : here is mysqli ones
Comment #3
gilcot commentedthe rewrite impactes sub-componants : here is pgsql ones
Comment #4
webchickHi, please use the "unified diff" format (cvs diff -up > filename.patch) and roll all patches into one where it makes sense. Where it doesn't make sense, they should be separate issues.
If the code you're changing is the same in the CVS version, the patch should be rolled against that version first, then back-ported.
Comment #5
webchickAnd actually, if I'm reading the patch correctly it looks like it changes APIs, which means it is definitely not for the stable version. HEAD is frozen now as well, but you can roll the patch and it can be postponed until next time HEAD is open for development again.
Comment #6
gilcot commentedwell. I didn't put a look on cvs code and the changes were only tested with 4.7.3 and 4.7.2 But it's compatible with CVS :)
Yes it changes APIs, but nothing change for module developpers.
Comment #7
bdragon commentedI believe that the db stuff got refactored a bit for 6. Drupal 7 will probabaly have a rewrite of the entire subsystem, so I'm just going to go ahead and close this...