Mo :ferris: :tux: @ FOSDEM on Nostr: I am just used to using the same type for a reference. Why can't #PostgreSQL at least ...
I am just used to using the same type for a reference.
Why can't #PostgreSQL at least throw a warning when one tries to use a serial type as a foreign key? I can't think of a case where it would make sense.
Maybe I am just too used to friendly error messages and warnings from #Rust by now…
#RustLang
Published at
2023-09-21 01:27:47Event JSON
{
"id": "f311a4b82173130e9bb199a4c91c9ea8e89d49093dc04863a520508f8d95c2ad",
"pubkey": "979383f8767c5d795fcad86f82dc7b38b384c1a473710c433014dc2c0fb0e359",
"created_at": 1695259667,
"kind": 1,
"tags": [
[
"e",
"ecad0b29e60cc8d78de41cc8435e9b57ffa405f2237d88c415bfd89c687914de",
"wss://relay.mostr.pub",
"reply"
],
[
"t",
"postgresql"
],
[
"t",
"rust"
],
[
"t",
"rustlang"
],
[
"proxy",
"https://fosstodon.org/users/mo8it/statuses/111100537551110986",
"activitypub"
]
],
"content": "I am just used to using the same type for a reference.\n\nWhy can't #PostgreSQL at least throw a warning when one tries to use a serial type as a foreign key? I can't think of a case where it would make sense.\n\nMaybe I am just too used to friendly error messages and warnings from #Rust by now…\n\n#RustLang",
"sig": "f07219f6faf6f7fe919396695c0b7757e6dfaec271ad1138d13df866196eb71630e5cccb0fc430a00955246375eca58dce61541e77fa8fe2cbc879697071d663"
}
