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'

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Dave Reid’s picture

Version: 6.9 » 7.x-dev
Priority: Normal » Minor
Status: Active » Needs review
FileSize
831 bytes
866 bytes

Good find. Here's patches for D7 and D6. Marking for D7 to be fixed first, then D6.

catch’s picture

Status: Needs review » Reviewed & tested by the community
Issue tags: +Quick fix
webchick’s picture

Version: 7.x-dev » 6.x-dev

Fixed in HEAD. :) Kicking back over to you.

Gábor Hojtsy’s picture

Status: Reviewed & tested by the community » Fixed

Thanks, committed to D6.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

lance.gliser’s picture

Status: Closed (fixed) » Needs review

The 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?

Dave Reid’s picture

Status: Needs review » Fixed

Because 'unique keys' is the correct term? :) Please read the initial post and the first patch.

lance.gliser’s picture

That'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?

Status: Fixed » Closed (fixed)
Issue tags: -Quick fix

Automatically closed -- issue fixed for 2 weeks with no activity.