Home/ Questions/Q 8430889
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-10T05:42:28+00:00

I have many examples of this through my database. Below is a simple example

  • 0

I have many examples of this through my database. Below is a simple example you may be able to lend assistance with.

I have an Image table

image_src
street_number
steet_name
postcode
county
country
camera_used
title
description
date_time_taken
user_id

My question is to prevent duplicate data from being added such as camera which could be the same camera for multiple image I thought it best to separate the table.

However if a user then updates the camera in the camera_used table the id in each record would correspond to the updated camera across all images. Same situation with the address.

If this instance is it best to perform a check before the update to see if any other tables reference the id and if so create an insert if not update the record.

The situation is one user updates the camera, another uses think thats not my camera updates the record and back and to we go. Just was unsure if this the best way with one to many.

Image table at presententer image description here

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Don’t allow users to update the camera table, at least not directly.

    What they can do is update the camera used for their specific image which either finds the correct entry in camera or creates a new one. You don’t want to allow them to change the camera table directly at all or else it will change that camera for all images, as you indicated.

    • 0