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.
The key in the schema associative array to denote unique keys in a table, is wrongly mentioned as 'unique key' rather than 'unique keys' in the description at the top of http://api.drupal.org/api/group/schemaapi/6
Note that the example code has the right key value, i.e. 'unique keys'
Comment | File | Size | Author |
---|---|---|---|
#1 | 359918-schema-api-typo-D6.patch | 866 bytes | Dave Reid |
#1 | 359918-schema-api-typo-D7.patch | 831 bytes | Dave Reid |
Comments
Comment #1
Dave ReidGood find. Here's patches for D7 and D6. Marking for D7 to be fixed first, then D6.
Comment #2
catchComment #3
webchickFixed in HEAD. :) Kicking back over to you.
Comment #4
Gábor HojtsyThanks, committed to D6.
Comment #6
lance.gliser CreditAttribution: lance.gliser commentedThe documentation at: http://drupal.org/node/146939 still shows "unique keys".
I have access to edit the page. Does anyone know of a reason it should not be corrected?
Comment #7
Dave ReidBecause 'unique keys' is the correct term? :) Please read the initial post and the first patch.
Comment #8
lance.gliser CreditAttribution: lance.gliser commentedThat's very odd...
I don't doubt you. But I do have to ask.
I'm working on a 6.9 core and building a module schema at the moment.
While I was using 'unique keys' I received errors.
After finding this page I changed the schema to 'unique key' and it worked.
Is there some sort of legacy support built in for my apparently mistaken code?