Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
There is a hard code static names in sql table names. So if we use db_prefix for table name, we get error.
Could it be with {} instead?
Have a nice time with aegir ;o)
Comment | File | Size | Author |
---|---|---|---|
#3 | table_name_with_brackets-2.patch | 899 bytes | pokurek |
table_name_with_brackets.patch | 4.45 KB | pokurek |
Comments
Comment #1
pokurek CreditAttribution: pokurek commentedMoving this issue to the better project.
Comment #2
adrian CreditAttribution: adrian commentedthe current and target tables are temporary and are meant to be that way. they exist only for the session and shouldnt be modified.
additionally. it is highly highly highly recommended that you do NOT try to run aegir with db prefixing.
We will not be maintaining an upgrade path for this.
The curly brackets around the hosting_package tables are relevant though, and i will commit that change if you re-roll the patch.
Comment #3
pokurek CreditAttribution: pokurek commentedSorry, but I am not sure What You mean with re-roll the patch :o(
So I thing that brackets are important only in this case:
Comment #4
adrian CreditAttribution: adrian commentedcommitted to HEAD.
thanks.