If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Enjoy an ad free experience by logging in. Not a member yet? Register.

Sure, but that's simply a bad design. Use a many to many relationship by using a many to many or a many to one in order to flatten it into a normalized structure.
If an image can belong to multiple gallery, you'd use three tables, image, gallery and imagegallery (or whatever names you want). If an image can belong to one and only one gallery, than you'd add a property on the image table to relate it to the gallery.

PHP Code:

header('HTTP/1.1 420 Enhance Your Calm');

Been gone for a few months, and haven't programmed in that long of a time. Meh, I'll wing it ;)

Sure, but that's simply a bad design. Use a many to many relationship by using a many to many or a many to one in order to flatten it into a normalized structure.
If an image can belong to multiple gallery, you'd use three tables, image, gallery and imagegallery (or whatever names you want). If an image can belong to one and only one gallery, than you'd add a property on the image table to relate it to the gallery.

I'm not sure what you mean, my knowledge of SQL is limited but growing.

If a member can have multiple galleries, than you'll want to use similar to the one to many I have posted above, and then use the memberid to provide ownership to the gallery.
If you only allow one gallery per member, you could assign the image directly to a member exactly as old pedant has.

PHP Code:

header('HTTP/1.1 420 Enhance Your Calm');

Been gone for a few months, and haven't programmed in that long of a time. Meh, I'll wing it ;)