In a multisite environment where we have the sequences table shared, I discovered an entry in that table for path_access which did not follow the convention of using the db/table name prefixes. This presents a problem because each site has its own path_access table but they share the sequence. The prefixes would resolve that issue, so the code needs patching to handle this correctly. I also appended "_pid" to the table name to give the sequence a more descriptive name.
I attempted to address the Postgres handling of the sequence too but I do not have PG, so hopefully someone can test this on the PG side. It worked for me under MySQL.
I have included patches for the install and modules files separately here. I hope that is acceptable. Thanks!
| Comment | File | Size | Author |
|---|---|---|---|
| path_access.module.seqid_.patch | 630 bytes | MMachnik | |
| path_access.install.seqid_.patch | 1.68 KB | MMachnik |
Comments
Comment #1
MMachnik commentedNote -- this patch should only be applied when doing a new install of the module. An update will be needed to adjust the name of the sequence so it will work with existing installations.
Comment #2
joachim commentedI'm not sure what this does, but I'll just say I really don't like the look of a table name only partly within curly braces!