Edit Question - KnowledgeHub

Title Body

Currently I'm working on a RFID project where each tag is attached to an object. An object could be a person, a computer, a pencil, a box or whatever it comes to the mind of my boss. And of course each object have different attributes. So I'm trying to have a table tags where I can keep a register of each tag in the system (registration of the tag). And another tables where I can relate a tag with and object and describe some other attributes, this is what a have done. (No real schema just a simplified version) Suddenly, I realize that this schema could have the same tag in severals tables. For example, the tag 123 could be in C and B at the same time. Which is impossible because each tag just could be attached to just a single object. To put it simple I want that each tag could not appear more than once in the database. My current approach What I really want Update: Yeah, the TagID is chosen by the end user. Moreover the TagID is given by a Tag Reader and the TagID is a 128-bit number. New Update: The objects until now are: -- Medicament(TagID, comercial_name, generic_name, amount, ...) -- Machine(TagID, name, description, model, manufacturer, ...) -- Patient(TagID, firstName, lastName, birthday, ...) All the attributes (columns or whatever you name it) are very different. Update after update I'm working on a system, with RFID tags for a hospital. Each RFID tag is attached to an object in order keep watch them and unfortunately each object have a lot of different attributes. An object could be a person, a machine or a medicine, or maybe a new object with other

Tags (comma-separated) Cancel