Hello All,
3I had found a music collection from Meloman, to analyse how it's build as a rookie. It has a strange Id key. It looks it has only a key and not a ID. What is the reason here for? See attachments
Music Collection with strange ID
Re: Music Collection with strange ID
I think you refers to this:
https://wiki.openoffice.org/wiki/MusicD ... esentation
If after read the "Meloman User Guide" you do not find other solutions, you may try to contact the Author.
https://wiki.openoffice.org/wiki/User:VladS_HitekSchool
https://wiki.openoffice.org/wiki/MusicD ... esentation
If after read the "Meloman User Guide" you do not find other solutions, you may try to contact the Author.
https://wiki.openoffice.org/wiki/User:VladS_HitekSchool
openoffice 4.1.6 - Windows 10
-
- Volunteer
- Posts: 1547
- Joined: Wed Jun 24, 2015 12:56 am
- Location: Colorado, USA
Re: Music Collection with strange ID
After taking a quick look at that database, it is probably not a good example for someone new to databases, unless you are looking to see an example of questionable design decisions.
There are a number of tables that use Text (VARCHAR) fields as a primary key, which is often not a good choice. For instance tblAlbum has AlbumName as the primary key. That means that each AlbumName value must be unique, but in the real world that is not always true. That forces the user to adopt some sort of ad hoc naming scheme when they encounter duplicate album names.
Some designers use Text (VARCHAR) fields as a primary key, naively thinking there is some sort of economy in that. But that just forces the database engine to create an additional index into the table at runtime. Integer comparisons are quick and easy while string comparisons are not.
In most cases it is better to use the default Integer field named ID with the Auto Value property set to TRUE/Yes.
tblYear might be an example where the field Year makes a good Primary Key.
There are a number of tables that use Text (VARCHAR) fields as a primary key, which is often not a good choice. For instance tblAlbum has AlbumName as the primary key. That means that each AlbumName value must be unique, but in the real world that is not always true. That forces the user to adopt some sort of ad hoc naming scheme when they encounter duplicate album names.
Some designers use Text (VARCHAR) fields as a primary key, naively thinking there is some sort of economy in that. But that just forces the database engine to create an additional index into the table at runtime. Integer comparisons are quick and easy while string comparisons are not.
In most cases it is better to use the default Integer field named ID with the Auto Value property set to TRUE/Yes.
tblYear might be an example where the field Year makes a good Primary Key.
If your problem has been solved, please edit this topic's initial post and add "[Solved]" to the beginning of the subject line
Apache OpenOffice 4.1.14 & LibreOffice 7.6.2.1 (x86_64) - Windows 10 Professional- Windows 11
Apache OpenOffice 4.1.14 & LibreOffice 7.6.2.1 (x86_64) - Windows 10 Professional- Windows 11
Re: Music Collection with strange ID
UnkDonald418,
THX for the replay. Thats I wanna know.
THX for the replay. Thats I wanna know.
Open Office 3.1 on Linux Mint 20.2