![]() | |
#1
| |||
| |||
|
|
Informally I think of abstract identifiers as "internal glue" within a relational database. A bit more formally, they are characterised as identifiers that could be mapped bijectively to different values throughout the database without changing the recorded information. One would therefore hope that they aren't visible to end users. I have wondered for some time whether abstract identifiers are only needed within the confines of a flat relational model. The following hypothetical example is meant to cast some light on this question. I'm hoping you'll see the underlying matters of principle and see how it raises some interesting questions and ideas: Let a cardboard box of items land on your desk and your task is to record information about the items in a database. In theory each item is uniquely identified by its (x,y,z) position at any given epoch. However, the idea is that the items are mixed up in the box and their positions are irrelevant to the information that needs to be recorded. The items are not labelled. The idea is to uniquely identify them (only) by their observable properties. This is indeed assumed to be an important integrity constraint to be enforced by the DBMS. Note as well that it would be upsetting (and potentially very costly or impractical) if the database system forces items to be labelled when there shouldn't be a need to. |
#2
| |||
| |||
|
|
Consider two electrons. They both have the same mass, and they have the same charge. They might have opposite spins. But the minute we add a third electron, the spin of two of them is going to be identical. It seems that, on the surface at least, electrons do not have enough properties to carry identity. As you descend into lower level particles like quarks, things get even more this way. Particles seem more and more interchangeable. Subatomic particles might not have much to do with your objects in a box, but it seems to me that any theory of reality and identity that falls apart at the subatomic level should at least take that into account. |
#3
| |||
| |||
|
|
On Jun 5, 1:25 pm, "Walter Mitty" <wami... (AT) verizon (DOT) net> wrote: Consider two electrons. They both have the same mass, and they have the same charge. They might have opposite spins. But the minute we add a third electron, the spin of two of them is going to be identical. It seems that, on the surface at least, electrons do not have enough properties to carry identity. If objects are really not distinguishable then why someone would want to artificially identify them? Wouldn˘t be better to record just their quantity? |
#4
| |||
| |||
|
|
Consider two electrons. They both have the same mass, and they have the same charge. They might have opposite spins. But the minute we add a third electron, the spin of two of them is going to be identical. It seems that, on the surface at least, electrons do not have enough properties to carry identity. If objects are really not distinguishable then why someone would want to artificially identify them? Wouldn’t be better to record just their quantity? |
#5
| |||
| |||
|
|
On Jun 5, 1:25 pm, "Walter Mitty" <wami... (AT) verizon (DOT) net> wrote: Consider two electrons. *They both have the same mass, and they have the same charge. *They might have opposite spins. *But the minute we add a third electron, the spin of two of them is going to be identical. *It seemsthat, on the surface at least, electrons do not have enough properties to carry identity. If objects are really not distinguishable then why someone would want to artificially identify them? Wouldn’t be better to record just their quantity? |
#6
| |||
| |||
|
|
robur.6 (AT) gmail (DOT) com> wrote in message news:edb2d328-6d69-4273-a5ab-99c3b0f50ff5 (AT) v4g2000vba (DOT) googlegroups.com... On Jun 5, 1:25 pm, "Walter Mitty" <wami... (AT) verizon (DOT) net> wrote: Consider two electrons. They both have the same mass, and they have the same charge. They might have opposite spins. But the minute we add a third electron, the spin of two of them is going to be identical. It seems that, on the surface at least, electrons do not have enough properties to carry identity. If objects are really not distinguishable then why someone would want to artificially identify them? Wouldn't be better to record just their quantity? Good point. So there are some case where identity is not important. (Incidentally, the other response where the comment was made that two electrons must occupy different states leads to a slippery slope. Using state to identify implies that a change of state is in effect a change of identity. This is related to Brian's claim that all attributes of an entity are mutable. (Am I misinterpreting your claim, Brian?) |
#7
| |||
| |||
|
|
In other words the abstract identifiers can actually be seen as providing a curious means to encode the number of indistinguishable items in the cardboard box. |
#8
| |||
| |||
|
|
"David BL" <davi... (AT) iinet (DOT) net.au> wrote in message news:03132046-3fd2-4bb1-9e00-cd81ece451c2 (AT) h2g2000yqg (DOT) googlegroups.com... Informally I think of abstract identifiers as "internal glue" within a relational database. *A bit more formally, they are characterised as identifiers that could be mapped bijectively to different values throughout the database without changing the recorded information. One would therefore hope that they aren't visible to end users. I have wondered for some time whether abstract identifiers are only needed within the confines of a flat relational model. *The following hypothetical example is meant to cast some light on this question. I'm hoping you'll see the underlying matters of principle and see how it raises some interesting questions and ideas: Let a cardboard box of items land on your desk and your task is to record information about the items in a database. *In theory each item is uniquely identified by its (x,y,z) position at any given epoch. However, the idea is that the items are mixed up in the box and their positions are irrelevant to the information that needs to be recorded. The items are not labelled. *The idea is to uniquely identify them (only) by their observable properties. *This is indeed assumed to be an important integrity constraint to be enforced by the DBMS. *Note as well that it would be upsetting (and potentially very costly or impractical) if the database system forces items to be labelled when there shouldn't be a need to. Consider two electrons. *They both have the same mass, and they have the same charge. *They might have opposite spins. *But the minute we add a third electron, the spin of two of them is going to be identical. * |
#9
| |||
| |||
|
|
"David BL" <davi... (AT) iinet (DOT) net.au> wrote in message news:03132046-3fd2-4bb1-9e00-cd81ece451c2 (AT) h2g2000yqg (DOT) googlegroups.com... Informally I think of abstract identifiers as "internal glue" within a relational database. *A bit more formally, they are characterised as identifiers that could be mapped bijectively to different values throughout the database without changing the recorded information. One would therefore hope that they aren't visible to end users. I have wondered for some time whether abstract identifiers are only needed within the confines of a flat relational model. *The following hypothetical example is meant to cast some light on this question. I'm hoping you'll see the underlying matters of principle and see how it raises some interesting questions and ideas: Let a cardboard box of items land on your desk and your task is to record information about the items in a database. *In theory each item is uniquely identified by its (x,y,z) position at any given epoch. However, the idea is that the items are mixed up in the box and their positions are irrelevant to the information that needs to be recorded. The items are not labelled. *The idea is to uniquely identify them (only) by their observable properties. *This is indeed assumed to be an important integrity constraint to be enforced by the DBMS. *Note as well that it would be upsetting (and potentially very costly or impractical) if the database system forces items to be labelled when there shouldn't be a need to. Consider two electrons. *They both have the same mass, and they have the same charge. *They might have opposite spins. *But the minute we add a third electron, the spin of two of them is going to be identical. *It seems that, on the surface at least, electrons do not have enough properties to carry identity. |
|
*As you descend into lower level particles like quarks, things get even more this way. *Particles seem more and more interchangeable. Subatomic particles might not have much to do with your objects in a box, but it seems to me that any theory of reality and identity that falls apart at the subatomic level should at least take that into account. |
#10
| |||
| |||
|
|
Then how would you know there were three electrons at all. Magic? |
![]() |
| Thread Tools | |
| Display Modes | |
| |