Originally Posted by Fou-Lu
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.