As Sorex said, you are not doing this "the database way".
I hope this does not come across as a snark, because it's not intended that way, but you'll save yorself a lot of trouble if you grab a book on the subject of databases and learn how to design and use databases properly.
It's also a very valuable skill to have professionally. Almost all larger projects have a database in it somewhere, and the demand for people who are good at databases is much larger than the supply.
What's wrong in your current solution:
You are storing calculated information that could easily and efficiently be obtained on the fly by joining the two tables. Never, ever store calculated information unless there is a very compelling reason to do so. Sooner or later, you'll end up in a situation where things get out of sync, where the calculated field don't match the data it's based on.
Also, you don't seem to have a relation between the tables. This means that the database won't stop you from storing images for non-existing items, or deleting items without deleting their images. You may think that you can stop that from happening in code, but, trust me, it will happen. Tables that are not related to any other tables are usually a clear symptom of a bad database design.
I would do the tables like this:
Stores:
ItemID
Location
Price
Images:
ImageID (You always want a unique ID on each record)
ItemID
Image (as a blob)
Then added a relation between the two ItemIDs.
Then, you can, for example, simply get all images for an item by something like:
select Image from Images join Stores on Images.ItemID = Stores.ItemID where ItemID = ItemIAmLookingFor;
If you don't get any rows returned, there was no images.
Edit: A good "lab environment" to fiddle around with databases is Microsoft Access. It allows you to quickly build tables, set up relations and has a quite powerful query builder which allows you to make complicated SQL statements in no time. I've worked with databases for decades, and still use Access to build my more complicated SQL statements.