News for hackers. Stuff that matters.
Re:What does First Normal Form mean? by whatshisface on Friday June 18, 2021 @11:34AM (#27551444)
I have never understood why RDBs have such general concepts of primary keys, where you can for example let date of birth be a primary key, when in every schema I have ever designed or seen, all rows get unique integer IDs anyway.
Re:What does First Normal Form mean? by mamcx on Friday June 18, 2021 @12:06PM (#27551803)
> when in every schema I have ever designed or seen, all rows get unique integer IDs anyway.

This is artifact of 4 things:

- Indexed Integer search are fast in RDBMS

- Having an non-bussines related value for identify a row could save you from making triggers for updated in other relations if it change. This is the part a lot of folks missed: If you already have a natural PK and it not change, is wasteful add ANOTHER (is another index btw)

- Is enforced by ORMS that are badly designed.

- Most people have not idea how model a database, and this one little thing is one of the easier "fix" you can think of!

I have done a lot "non integer primary keys" before (and not GUIds!) and is useful that RDBMS are not like mongo with a fixed schema (yes! Mongo is a single fixed-schema for all your data!).

For reporting, store aggregates, pre-compute values, etc is very valuable!

For example, in accounting you do reports per day/mont/year.

You then do granularity per day, and the another per month, per year, per semestre, etc. When the data volume is high, making tables "days, months, years" make a lot of sense.

Cool guys call this a "time-series database".

But the rdbms CAN model it!

And can model

- "document database"

- "key-value database"

- "olap database"

- "columnar database"

etc.

(you go for specialized backend for performance but honestly? Most of the time is a mistake if them are not relational.

"Relational" don't means "is backed by b-trees, is row oriented and use SQL")

Re:What does First Normal Form mean? by whatshisface on Friday June 18, 2021 @12:26PM (#27552023)
A time series database isn't keyed by day/month/year, it's typically keyed by monotonic timestamps.
Re:What does First Normal Form mean? by mamcx on Friday June 18, 2021 @12:34PM (#27552121)
Yes, that is even a more narrowing detail. (people that use a "time-series" rarely need that high of granularity!)

But the question was about wondering "why exist the support for PK that are not integers/guis, like dates"?.

To be able to model a lot of things for what in the past (before RDBMS) and today (for upstarts engines) you will be tempted to add another data store (that rarely is that necessary).

I know by a fact that some times is because people not realize you DON'T need to constrain your db to things like "only integers pks!"!

P.D: I work in the enterprise sector. Is fun when something is composed of a cluster of disparate things purely by misunderstanding you could have solved it with a simple db, well done. Contrary to belief, a lot of my customers, their largest databases are 1-10GB each. A rdbms can happily go much much larger than that, if you give them a little love...

Re:What does First Normal Form mean? by jrumbut on Friday June 18, 2021 @12:40PM (#27552208)
It's wonderful what you can gain in performance, correctness, and storage efficiency from finding the real primary key from the data model itself.

Maybe not worth the intensive design work for many tables, and it can be a risk to get it wrong, but it's cool when it does work.

Re:What does First Normal Form mean? by brazzy on Friday June 18, 2021 @02:38PM (#27553447)
Yeah, I'm currently facing exactly that dilemma. I have to model a database of machine parts.

There is a natural PK in the form of the supplier's parts number, but the legacy system (which uses that as PK) notes that it is specifically the parts number as used in the supplier's ERP system, but suppliers often use differently formatted parts numers in publications such as catalogs (adding or removing spaces, slashes or dashes). So the legacy system also has the "published part number" as one or more separate fields.

This inconsistency makes me lean very strongly towards using a synthetic PK instead.

Re:What does First Normal Form mean? by CRConrad on Monday June 28, 2021 @03:24AM (#27658993)
> There is a natural PK in the form of the supplier's parts number, but ...

Or even better: Then the supplier revamps their parts numbering scheme, and every product gets a new number.

Re:What does First Normal Form mean? by bob1029 on Friday June 18, 2021 @02:51PM (#27553585)
We deal with a lot of crap where a certain business entity has several different biz keys that can reasonably be used to uniquely identify the thing.

I would concur with adding a synthetic primary key, and maintaining all of the relevant business/domain keys on the same type.

The advantage of this approach is that you can still keep 100% correct relations between your internal types, even if the domain keying scheme is fucked up or otherwise broken per your original assumptions. It's really easy to add a new column to refine the additional domain keys. Fixing a bad PK and all the things that talk to it is much harder.

Re:What does First Normal Form mean? by dnlhg on Friday June 18, 2021 @11:52AM (#27551641)
Codd was pretty adamant in his original papers that keys should be made up from data rather than a unique integer, and his example of converting from a hierarchical database schemas to a relational database schema shows how compound, natural keys are important to represent relationships. But we don’t usually do it that way today, partly because it isn’t that practical with our current databases and ORMs. It has some theoretical advantages and disadvantages, but using IDs seems to work well enough that we’re not investing in a new paradigm.
Re:What does First Normal Form mean? by wwweston on Friday June 18, 2021 @12:18PM (#27551923)
Yeah, I think the early proponents of relational models had a lot to do with setting the culture here.

I suspect that some of this has to do with an insight I recently discovered: a "natural" key is in some sense a key that's so foreign it's in a "database" you don't control. And if you establish a culture that converges on natural keys, you may end up with more easily cross-operable databases/collections as an asset.

And this is why I think it's probably dead. If the boring practicality of generated identifiers didn't do it, laws like the CCPA which are going to, because they recognized the potential of broad cross-operable data to be a liability and a hazard vs an asset.

Re:What does First Normal Form mean? by whatshisface on Friday June 18, 2021 @12:22PM (#27551968)
Those "natural" databases as a rule are going to be full of duplicates and sometimes even inconsistencies, hence the need for IDs that only exist for the purpose of expressing relationships within your own database. Basically, pointers.
Re:What does First Normal Form mean? by CRConrad on Monday June 28, 2021 @03:25AM (#27658994)
Re:What does First Normal Form mean? by ARandumGuy on Friday June 18, 2021 @04:49PM (#27554875)
In practice, using a unique IDs is often not ideal, but it also rarely the wrong choice. I've personally never heard of a scenario where a unique ID caused difficult to fix issues (although I'm sure it's possible).

In contrast, a poorly though out natural key can cause a lot of headaches. This mostly occurs when your natural key isn't as unique as you thought, or if you have to change what you use as a natural key. The real world does not like to conform to our database constraints.

Re:What does First Normal Form mean? by goto11 on Saturday June 19, 2021 @04:38AM (#27558900)
Codd actually use a synthetic identifier for employee ID in an example in the original paper. So I don't think he is against synthetic identifiers in principle. But if a natural key exist of course a synthetic key need not be introduced.
Re:What does First Normal Form mean? by adrianmonk on Friday June 18, 2021 @03:32PM (#27553997)
What you're talking about is a natural key[1], which can be contrasted with a surrogate key[2]. (Surrogate keys are also called "synthetic keys" or "factless keys".)

So the question is whether natural keys are ever useful.

I think the answer is yes, they are useful if the real world already imposes a key on the stuff you are modeling in the database. In that case, it is already unique (as it needs to be), and generating your own key doesn't accomplish anything (but is redundant).

For example, suppose I'm creating a history database of who owned what internet domain names at which times. If my table is one-to-one with domains, I can use the domain name itself as the primary key.

If not, I can perhaps use the domain name plus some other column as a composite key. For a table of ownership intervals, my primary key could be this: domain name + start date + end date.

---

[1] https://en.wikipedia.org/wiki/Natural_key

[2] https://en.wikipedia.org/wiki/Surrogate_key

Re:What does First Normal Form mean? by whatshisface on Friday June 18, 2021 @04:11PM (#27554425)
>For example, suppose I'm creating a history database of who owned what internet domain names at which times. If my table is one-to-one with domains, I can use the domain name itself as the primary key.

In your example, wouldn't that not work, because the same domain would be in the table twice with two different owners?

Re:What does First Normal Form mean? by adrianmonk on Friday June 18, 2021 @04:29PM (#27554655)
You might have more than one table in the database. For example, you could have a table of current owners for quick lookup and a table of all owners for full history.

For the current owners table, you'd use just the domain as a key. For all the full history table, you'd use domain + start date + end date as the key.

So yeah, that makes it a weird example, but the point is that in neither table did you make up a synthetic key. In one table, you used a real-world fact (domain) as the key, and in the other table you used three real-world facts (domain plus two dates) together as a key.

Re:What does First Normal Form mean? by turbocon on Friday June 18, 2021 @11:46AM (#27551570)
It's rare in practice but occasionally rows have natural unique identifiers that are useable.

The textbook case would be student IDs in a university database where each row corresponds to a single student. However some universities view the student id as sensitive information (kind of like a ssn in the US) and so in that scenario it should be aliased to some other key to prevent the student id from being present in multiple tables as a foreign key.

Re:What does First Normal Form mean? by bart_spoon on Friday June 18, 2021 @07:32PM (#27556222)
I think a natural key that I’ve encountered is a database containing professional NBA data. Teams never play more than once per day, and there are only two teams in the game, so a natural (composite) key for games is simply the date of the game and the two teams that played. You can create a “game ID” if you wish, but you aren’t actually doing anything but adding a column of redundant information.
Re:What does First Normal Form mean? by jameshart on Friday June 18, 2021 @12:38PM (#27552176)
Student IDs are certainly not ‘natural’ keys.

I am almost entirely convinced that there is actually no such thing as a natural key.

Re:What does First Normal Form mean? by wolfgang42 on Friday June 18, 2021 @02:45PM (#27553522)
a "natural key" is frequently just a really foreign key in a database you and your org don't manage. — 'wweston, https://news.ycombinator.com/item?id=27349246
Re:What does First Normal Form mean? by mulmen on Friday June 18, 2021 @02:31PM (#27553374)
Natural keys are everywhere. They are just less interesting than the relationships. My name is a natural key. It uniquely identifies my name. The wheels come off if you expect it to uniquely identify me. But with natural keys that's never actually necessary.

When I buy a car they record my name, my date of birth, the time of the sale and some details about the car, such as the VIN, which is its name. That provides enough information to form a natural key to identify the sale.

At no point does a database actually have a concept of who I am really, only the relevant data points to satisfy its own relational model.

Any database that means to track information about people would be able to construct a natural key from my name, my mothers name and some information about my birth, such as the doctor, hospital and time.

Re:What does First Normal Form mean? by jameshart on Saturday June 19, 2021 @11:18AM (#27561224)
(Interesting cultural assumption there that people are born in hospitals under the supervision of doctors)

The thing is to qualify as a natural key I think it has to be precisely recoverable just from first principles wherever you encounter the artifact it references. The birth details aren’t inherent to the person, they’re datapoints about them.

All the identifiers you propose to make up mnatural’ keys are synthetic keys from some other authority for identifying things. VINs obviously are synthetic identifiers, but so are names, dates, hospital addresses.

As you rightly say, a string is a natural key for itself; likewise a number.

The only other ‘natural key’ I can think of is atomic number for identifying chemical elements.

Re:What does First Normal Form mean? by mulmen on Saturday June 19, 2021 @03:24PM (#27563591)
I said a database that tracks people could identify me using information about my birth. Not that everyone is born in a hospital or by a doctor.

By your definition there are no natural keys. But since that definition isn't useful we instead use one that is. The natural key is the identifier by which the thing is already known.

https://en.wikipedia.org/wiki/Natural_key

Re:What does First Normal Form mean? by CRConrad on Monday June 28, 2021 @07:41AM (#27660550)
> I said a database that tracks people could identify me using information about my birth.

And your name, you said.

> The natural key is the identifier by which the thing is already known.

And then you change your name.

Re:What does First Normal Form mean? by denton-scratch on Saturday June 19, 2021 @11:55PM (#27566947)
Probably not unique, though. Well, yours might be; but in general, a person's name isn't a reliable unique identifier. Nor anyone's name. Even if you have a timestramp, you can't be sure it's unique.
Re:What does First Normal Form mean? by dragonwriter on Friday June 18, 2021 @06:50PM (#27555875)
Dates are natural keys in a calendar table. The composite of the foreign key values is a natural key in a join table expressing a unique relationship between entities in two or more other tables, perhaps with additional attributes, even if those values are surrogate keys in their own tables.
Re:What does First Normal Form mean? by jameshart on Saturday June 19, 2021 @11:08AM (#27561098)
Dates aren’t natural. I know of at least three different date keys in different calendars that refer to the same calendar day - choosing to use one particular date standard to refer to days is choosing a pre-existing synthetic key, not a ‘natural’ one.
Re:What does First Normal Form mean? by dragonwriter on Sunday June 20, 2021 @10:51AM (#27570578)
> I know of at least three different date keys in different calendars that refer to the same calendar day

Aside from the fact that you have very limited knowledge of calebdar systems, I’m not sure what this is supposed to prove. “Natural” in “natural key” doesn't mean “exists in nature outside of human invention”, it means “exists outside the database as part of the data in the data model, rather than being created solely to have a ubique key in the database ubder design".

The date in whatever particular calendar system is used in the data model is a natural key for a calendar table.

Re:What does First Normal Form mean? by mulmen on Saturday June 19, 2021 @03:42PM (#27563745)
Dates are natural keys.

You seem to be conflating format and value. 1,234,567 and 1234567 are the same number. 19-Jun-21 and 2021-06-19 are the same date. Databases already handle this.

Re:What does First Normal Form mean? by jameshart on Saturday June 19, 2021 @04:36PM (#27564243)
19 June 2021 is also known as:

Dhuʻl-Qiʻdah 9, 1442 AH

9 Tamuz 5781

Re:What does First Normal Form mean? by mulmen on Saturday June 19, 2021 @04:41PM (#27564284)
Great! Then if they are unambiguous they can be inserted directly or disambiguated and then inserted. At query time any format can be used to represent them to a user.
Re:What does First Normal Form mean? by jameshart on Saturday June 19, 2021 @04:54PM (#27564382)
Ah, so you're suggesting instead of storing 'what a person calls this date' as the key, you instead convert it to some underlying representation that you can then choose to present in different calendars - like a UNIX epoch-relative offset or something.

Congratulations, you just created another synthetic key for describing dates.

Re:What does First Normal Form mean? by goto11 on Monday June 21, 2021 @03:51AM (#27577164)
That is not what synthetic key means. A synthetic key is a key which does not carry any information, like an auto-incremented integer. A date is a natural key, regardless of the underlying representation.
Re:What does First Normal Form mean? by mulmen on Saturday June 19, 2021 @05:24PM (#27564586)
The date is a natural key. The format string is only a representation. Implementation details are irrelevant to the definition of a natural key.
Re:What does First Normal Form mean? by CharlesW on Friday June 18, 2021 @02:35PM (#27553413)
> I am almost entirely convinced that there is actually no such thing as a natural key.

Yes! Or if it is now, there's a future scenario where that will have proven to have been a poor decision.

Re:What does First Normal Form mean? by dragonwriter on Friday June 18, 2021 @06:54PM (#27555898)
> The textbook case would be student IDs in a university database where each row corresponds to a single student

“Student IDs” are an example of surrogate keys, though they may be surrogate keys in a system predating and outside of the DB.

(And if the mapping between them and actual students are managed by an error-prone process outside of the DB, they probably aren’t good primary keys for a table of students.)

Re:What does First Normal Form mean? by TeMPOraL on Friday June 18, 2021 @11:49AM (#27551615)
> However some universities view the student id as sensitive information (kind of like a ssn in the US) and so in that scenario it should be aliased to some other key to prevent the student id from being present in multiple tables as a foreign key.

It is ironic, given that the whole reason to have a student ID is for it to be a primary key in some database somewhere.

Re:What does First Normal Form mean? by whatshisface on Friday June 18, 2021 @12:31PM (#27552088)
Databases are vulnerable to a particular type of folkloric magic:

https://en.m.wikipedia.org/wiki/True_name

Re:What does First Normal Form mean? by wombatpm on Friday June 18, 2021 @05:33PM (#27555273)
In the 1980's your student ID was most likely your SSN
Re:What does First Normal Form mean? by projektfu on Friday June 18, 2021 @12:45PM (#27552266)
In one sense, the unique integer is often not real data. It’s synthetic and has no meaning outside the application.

I find it easier to understand when I think that Codd and other database pioneers were looking at creating universal databases, not the application-specific ones we tend to use.

Furthermore, the use of auto numbering tends to make the queries easier to write but the tables less meaningful. For example, INVOICE might have a sequential invoice id that is real information, as well as a reference to customer, billing address, shipping address, etc. INVOICE_ITEM will have a foreign key to an invoice, unique number, position, stock item id (second foreign key), description, etc. PACKING_LIST might have a foreign key to INVOICE_ITEM. In my opinion, I prefer to see INVOICE_ID as part of the primary key of INVOICE_ITEM. I like being able to see the relationship in foreign keys and things like that.

These things can be a heated topic and other designers probably think I also like to murder kittens. But the data layout is, I think, what Codd was going for.

Re:What does First Normal Form mean? by dragonwriter on Friday June 18, 2021 @12:43PM (#27552244)
> I have never understood why RDBs have such general concepts of primary keys, where you can for example let date of birth be a primary key, when in every schema I have ever designed or seen, all rows get unique integer IDs anyway.

Because sequential integer surrogate keys aren't always a good idea, e.g.:

1. Certain logically-unique join tables, where the foreign keys to the joined tables form an obvious composite primary key.

2. Cases with natural primary keys for basic data; A date might not be a good primary key if its the DoB in a table of people, but its an excellent primary key in a calendar table.

3. Even when you need surrogate keys, sometimes you need them to be able to be generated in a distributed manner, so you want something like UUID/ULID instead of sequential integers.

Re:What does First Normal Form mean? by mmcgaha on Friday June 18, 2021 @12:18PM (#27551920)
I completely agree with you, yet I design most of my schemas with integer keys anyway. The only thing I do different than most folks is that I make a unique constraint/index for candidate keys (the proper primary key) because otherwise we have lost the ability to ensure data consistency.

As for why I use integer keys, it has always been the convention everywhere I go so I don't want to break convention.

Now the only convention that I would rather see would be to use GUIDs instead of integers because I hate that I can join an item table to an employee table and get results back.

Re:What does First Normal Form mean? by dylan604 on Friday June 18, 2021 @11:55AM (#27551675)
How would DoB work as a primary key? A primary key is useless if not unique, right? And I know many people born on the same day that aren't even twins. Incrementing integers are nice and easy for humans to consume. Using GUIDs is far more portable than unique integers, but damn near impossible for humans to deal.
Re:What does First Normal Form mean? by whatshisface on Friday June 18, 2021 @12:18PM (#27551930)
They wouldn't, so my point is why do RDBMSs support so many kinds of primary keys?
Re:What does First Normal Form mean? by dylan604 on Friday June 18, 2021 @12:25PM (#27552003)
Keys can span multiple columns, so DoB could be a differentiator if First, Last are also the same. I personally would never try to build a key like that though, but that's the only way I could see justifying its use.

If you can't see a why for uses of a field that is truly more unique, then I'd suggest you just need some more imagination. Strictly not allowing it seems to me to be short sighted just because someone had the ill conceived idea to use DoB as a primary key

Re:What does First Normal Form mean? by whatshisface on Friday June 18, 2021 @12:28PM (#27552058)
Can you think of any good use case for a non-arbitrary primary key? You are right that first name + last name + dob is not a good way to design the system. For example someone could differentiate their twin children only by their middle name. So, what's an example of a non-integer non-arbitrary primary key?
Re:What does First Normal Form mean? by bart_spoon on Friday June 18, 2021 @07:39PM (#27556293)
I stated this elsewhere, but with some sports data, you don’t gain anything with a uniquely generated game ID. NBA teams will only play one game at most per day, and only play one other team, so if you make a key of the date and the teams playing, you uniquely identify every event. You can create an arbitrary ID for a game if you want, but it’s not actually giving you information you don’t have, and therefore is entirely redundant.
Re:What does First Normal Form mean? by ipaddr on Friday June 18, 2021 @10:40PM (#27557273)
Using a generated pagename as a key.

You create a cms. You store each page with a 16 character name as the key and you use that as the url/pagename.

What about storing the ip for login attempts. You store the ip and date and use that information to rate limit. The ip is the primary id.

Password reset, you store the unique code you sent in the email as the key.

Country codes. The 2 or 3 short name makes as a key over a number if you want to limit joins.

Bitcoin key.

Anything token, key related, anywhere where you want to enforce no duplicates like a ssn.

Re:What does First Normal Form mean? by brantam on Friday June 18, 2021 @11:54PM (#27557603)
> Can you think of any good use case for a non-arbitrary primary key?

Login names; Vehicle registration numbers; flight numbers; domain names; file names; ip addresses. Keys are used in those cases where the enforcement of uniqueness is important for data integrity and identification purposes.

Re:What does First Normal Form mean? by dylan604 on Friday June 18, 2021 @01:22PM (#27552670)
Not sure exactly what you mean by non-arbitrary primary key, but...

GUID/UUID

FeatureName/ReleaseYear or Series/Season/Episode

email

phone-number

SSN

driverslicense#/State

Re:What does First Normal Form mean? by brazzy on Friday June 18, 2021 @02:45PM (#27553526)
Since when is "date of birth" a distinct type?

And "date" definitely does make sense as a primary key when you have a table that has conceptually at most one entry per day. For example, a travel journal. Or a time sheet application.

Re:What does First Normal Form mean? by cyberbanjo on Friday June 18, 2021 @11:37AM (#27551486)
What about people with the same birthdays?
Re:What does First Normal Form mean? by wfriesen on Friday June 18, 2021 @11:44AM (#27551556)
Business/requirements/users will often tell you that no two users will have the same birthday/SSN/whatever, but so often that eventually proves incorrect. Just using an auto increment ID as the primary key can prevent a lot of pain down the road.
Re:What does First Normal Form mean? by lifepillar on Friday June 18, 2021 @03:39PM (#27554068)
So, when someone comes to you and identifies herself by providing her SSN, name, date of birth, how do you know whether she corresponds to the record with id M or to the record with id N? Or, more likely, to one of the N records, with N>2, with that SSN, name, date of birth?
Re:What does First Normal Form mean? by ARandomerDude on Friday June 18, 2021 @11:52AM (#27551639)
I think this was the parent's point. Since, as you point out, we we almost never use the data itself (e.g. date of birth) as the primary key, the parent is asking why is this a feature at all? Why not just mandate a uuid, number, etc. as the primary key?
Re:What does First Normal Form mean? by uDontKnowMe on Friday June 18, 2021 @02:43PM (#27553498)
Well it's easy enough to think of a situation where you would use a date as a primary key, for example time series data.
Re:What does First Normal Form mean? by jraph on Friday June 18, 2021 @11:46AM (#27551568)
What about them? Do they really exist, practically speaking?

At a quick glance on my databases, I see nothing of the sort.

Re:What does First Normal Form mean? by jcranmer on Friday June 18, 2021 @11:57AM (#27551695)
I share the same name and birthdate as another individual. It has actually caused me to be held up at the border before.
Re:What does First Normal Form mean? by jraph on Friday June 18, 2021 @12:00PM (#27551732)
What gave proof that you were not this individual in the end?
Re:What does First Normal Form mean? by ipaddr on Friday June 18, 2021 @10:44PM (#27557291)
But not birth time and birth location.
Re:What does First Normal Form mean? by lkuty on Friday June 18, 2021 @11:49AM (#27551608)
Re:What does First Normal Form mean? by jraph on Friday June 18, 2021 @11:52AM (#27551647)
Is there anything comparable to the birthday paradox, which includes years, by the way?

I would guess that you would need a big group of random people such that there is a high chance of having two people born the very same day.

Re:What does First Normal Form mean? by whatshisface on Friday June 18, 2021 @11:55AM (#27551680)
The birthday paradox threshold if years are included would be 23 people per year, rather than 23 people in your database. What that translates to in your database depends a lot the age demography of your userbase. If people live to be 100, and if I don't worry about the fact that some years will have more people than others even if they are randomly distributed (something that should go in to the model), that's about 2,300 people before you start expecting to see duplicate birthdays.
Re:What does First Normal Form mean? by cyberbanjo on Friday June 18, 2021 @11:53AM (#27551659)
I don't think the birthday problem accounts for year, but yet it's clear some people share the same birthdate, twins for example.
Re:What does First Normal Form mean? by Kranar on Friday June 18, 2021 @12:27PM (#27552026)
Are we seriously discussing whether in practice, two people can be born on the same day?
Re:What does First Normal Form mean? by jraph on Friday June 18, 2021 @06:10PM (#27555544)
This was an absurd joke. A person looking at their database using birth dates as a primary key can obviously only see people with different birth dates.
Re:What does First Normal Form mean? by juped on Friday June 18, 2021 @03:07PM (#27553762)
Synthetic primary keys like a unique integer ID assigned to a row are worse in theory - the id column isn't real data. They exist as a very common practical compromise for good reasons, but you should be aware you're compromising theory for practice.
Re:What does First Normal Form mean? by hknapp on Friday June 18, 2021 @12:27PM (#27552032)
I worked at a place that used decimals that auto incremented by 2
Re:What does First Normal Form mean? by kbelder on Friday June 18, 2021 @07:05PM (#27555983)
Smart. That allows them to insert new rows without messing up the ordering.