Closed (outdated)
Project:
Drupal core
Version:
7.x-dev
Component:
field system
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
12 Nov 2010 at 15:43 UTC
Updated:
20 Mar 2020 at 16:52 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
eclipsegc commentedUsing git for this since it's kind to me than CVS, hopefully this patch is fine.
Comment #2
eclipsegc commentedComment #3
yched commentedTrue.
Comment #4
effulgentsia commentedNice catch. This looks correct, but columns.fid.description also needs to be updated. Looks like image_field_schema() and taxonomy_field_schema() also need a 'foreign keys' entry. I'll leave that up to you whether to roll those into this patch, or create separate issues for them.
Comment #5
eclipsegc commentedI already filed a separate issue for taxonomy.
#970016: taxonomy_field_schema lacks any foreign key support
Will look into image, and put together another patch for file to fix the description.
Comment #6
eclipsegc commentedsorry about that
Comment #7
eclipsegc commentedOK, hopefully this makes everyone happier.
Comment #8
mlncn commentedVery nice. Schema correctness++
Comment #9
eclipsegc commentedThis should probably include the image field foreign keys as well.
Comment #10
yched commentedThanks !
Comment #11
webchickChange to schema means we need an upgrade path, no?
Comment #12
webchickActually, in discussing this more with chx, an update function here is unnecessary. No core db engines, nor any of the ones we could find in contrib, actually put FK information into the database itself, so updating the PHP here should be sufficient.
Committed to HEAD.
Comment #13
gábor hojtsyLooks like even though FK is not put into the database, descriptions are (at least with MySQL), so this needs an update function.