Path: ...!news.nobody.at!2.eu.feeder.erje.net!feeder.erje.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: rbowman <bowman@montana.com>
Newsgroups: comp.os.linux.misc,comp.os.linux.advocacy
Subject: Re: GIMP 3.0.0-RC1
Date: 4 Jan 2025 05:36:27 GMT
Lines: 27
Message-ID: <ltrvmrFg3ccU2@mid.individual.net>
References: <vkjmdg$30kff$1@dont-email.me> <CoubP.49797$DPl.41452@fx13.iad>
	<pan$4da7a$f7b58970$926e1064$15cef996@linux.rocks>
	<4f7tmjplbte7cnuh2pqrh1fufs4iatv3fd@4ax.com>
	<f6GcnYUuyu7qFfL6nZ2dnZfqnPidnZ2d@earthlink.com>
	<ubb0nj5ioc4r3gbqhmmiprdejtefj1j6mm@4ax.com> <67707879@news.ausics.net>
	<edc3cd22-5cbb-bb81-70e4-321c53d62162@example.net>
	<VibcP.22228$VnJ1.12797@fx44.iad>
	<a092fd3e-df3f-6c16-fc67-50321ba67dd1@example.net>
	<YNycP.37866$vfee.30336@fx45.iad>
	<366b4ad1-4849-d7a9-cade-67d1eba035c3@example.net>
	<gJScP.13176$XfF8.10959@fx04.iad> <FEYcP.131275$aTp4.70494@fx09.iad>
	<35a09fa5-08b1-8121-51c7-28d3aac1cd0f@example.net>
	<CaidP.24348$DPp5.20979@fx01.iad>
	<3002e7b9-095e-c292-1202-b151f7776587@example.net>
	<ltmbcmFjcgpU1@mid.individual.net>
	<ba6263f8-1e7f-5eb1-ae06-757f2ed7a018@example.net>
	<lto9qbFso18U3@mid.individual.net>
	<29193643-39b8-1ce6-b817-e91cea1112a5@example.net>
	<ltr9vjFd8opU1@mid.individual.net>
	<0ed198a8-22b7-59e1-0085-adfc50df9fed@example.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net /D1OrkWrjFt9302ZdUoZPw1ckcDHliFiAQCHAveNWNnRgcvWYt
Cancel-Lock: sha1:fYeOYAi9kn4FjXTFVjgff/Al6xU= sha256:TkYfnqKhwFr6ici7r4rHopv1FJFF80gt3/phA4o7lgQ=
User-Agent: Pan/0.149 (Bellevue; 4c157ba)
Bytes: 3016

On Sat, 4 Jan 2025 01:51:38 +0100, D wrote:

> I think all the ones that use traditional databases I encountered are
> using either mysql, mariadb or sql server for linux which I think was
> free for a while. Sql server for linux was a joke. The company was
> offered help to migrate to mysql or mariadb, refused, since they were
> microsoft loyalists, and continued to live with downtime every month,
> rather than switching.

MySQL lost it's shine when it was bought and part of the team forked off 
MariaDB. I've never used either. 

Esri's Workgroup configuration use SQl Server Express which is free. It 
works well with the limitation that a database cannot exceed 10GB. That's 
perfectly adequate for most of our sites since the only want data for 
their county. If you get greedy and want half the state it's time for the 
full SQL Server.

Where it falls short is when you're trying to store years of incident 
data. Depending on the site you might get five or six years  before you 
have to start purging. otoh the price is right compared to a DB2 or full 
server license.

It was a little rocky to begin with but Esri now works fine with 
PostgresSQL. For a long time the spatial extender package for DB2 was an 
extra cost option but it's included with the base license now.