On 5/22/25 20:23, Ray O'Donnell wrote:
On 22/05/2025 18:52, Achilleas Mantzios wrote:
Hi people
I'd like to know if people here know of or use any integrated
solution for all or some of the above. It would be nice if it
supported LDAP / OAuth 2.0 , integrate with plain vanilla git (not
git
On 5/22/25 20:33, Albrecht Dreß wrote:
Am 22.05.25 21:04 schrieb(en) Adrian Klaver:
On 5/22/25 10:52, Achilleas Mantzios wrote:
Hi people
I'd like to know if people here know of or use any integrated solution
for all or some of the above. It would be nice if it supported LDAP /
OAuth 2.0 , in
On 5/23/25 00:23, Justin Clift wrote:
On 2025-05-23 03:52, Achilleas Mantzios wrote:
Hi people
I'd like to know if people here know of or use any integrated
solution for all or some of the above. It would be nice if it
supported LDAP / OAuth 2.0 , integrate with plain vanilla git (not
githu
On 5/23/25 09:58, Wim Bertels wrote:
Justin Clift schreef op vr 23-05-2025 om 09:23 [+1000]:
On 2025-05-23 03:52, Achilleas Mantzios wrote:
Hi people
I'd like to know if people here know of or use any integrated
solution
for all or some of the above. It would be nice if it supported LDAP
/
OA
On 5/22/25 20:04, Adrian Klaver wrote:
On 5/22/25 10:52, Achilleas Mantzios wrote:
Hi people
I'd like to know if people here know of or use any integrated
solution for all or some of the above. It would be nice if it
supported LDAP / OAuth 2.0 , integrate with plain vanilla git (not
github
Thanks for the reply, Adrian!
I must have explained my problem poorly, sorry for that.
Let me present an imaginary scenario and hopefully that clears things up.
It's 2015 and you want to start a birdwatching club and want to keep track
of sightings in a postgres database.
To make sure that user
Foreign key "code tables" are ubiquitous in good database design; another
example is zip/postal codes and cities. Statuses are another standard
usage. Thus, what you're doing is absolutely bog-standard. (In your case,
I would add "taxonomy_edition" to the species table. You get more
information
Richard Zetterberg writes:
> In my head, this change would be instant and postgres would carry on like
> nothing happened and that the domain always had the type `text`. Is this a
> fools errand? Or could it actually make sense in this situation?
Yeah, I think you can probably get away with this
