Event JSON
{
"id": "be07aa2dc4bfec5ff7ee3bf6860f4201efff4d638b78b0d027a86dfbdf393af0",
"pubkey": "926def87b895122312a8a2134d88522a6f06801755aa762905ad73515e68343d",
"created_at": 1733521202,
"kind": 1,
"tags": [
[
"p",
"1604479596e7ce882205e22aca705d5359fb9a6eb1d8a18064ac901bd78cb776",
"wss://relay.mostr.pub"
],
[
"p",
"bc0f30bd2715afe1fd5b62705460cb04d49e1666dc8846b254ee36ed7bd396f0",
"wss://relay.mostr.pub"
],
[
"t",
"postgresql"
],
[
"t",
"django"
],
[
"proxy",
"https://indieweb.social/users/anthony/statuses/113608045546370602",
"activitypub"
]
],
"content": "Today I Learned with nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqzczy09vkul8gsgs9ug4v5uza2dvlhxnwk8v2rqry4jgph4uvkamqy708gf during a pairing session that:\n1. In a Unique Index, NULL values are considered distinct values by default in #PostgreSQL.\n2. PostgreSQL 15+ supports a `NULLS NOT DISTINCT` option to change that behaviour.\n3. #Django 5+ supports `nulls_distinct=False` on `UniqueConstraint` to create the unique index with that option.\n\nNeat!\n\nhttps://framapiaf.org/@tut_tuuut/113607537015184362",
"sig": "968e404b933731f1605719a76d3673a5467b0fac6eb9294b2eb7d6c10636341d5d6eefa685e7acc1e28a6d032a06578a8a121837dd97ee6a601fb99ba14b51e3"
}