1 |
On Tuesday, August 12, 2014 03:38:15 PM Alan McKinnon wrote: |
2 |
> On 12/08/2014 15:28, J. Roeleveld wrote: |
3 |
> > On 12 August 2014 14:06:07 CEST, Alan McKinnon <alan.mckinnon@×××××.com> |
4 |
wrote: |
5 |
> >> On 12/08/2014 11:10, Mick wrote: |
6 |
> >>> I recall the devs explicitly stating early enough in the KDE4 |
7 |
> >> |
8 |
> >> development that |
9 |
> >> |
10 |
> >>> sqlite is not man enough for the job and advising everyone to move |
11 |
> >> |
12 |
> >> over to |
13 |
> >> |
14 |
> >>> mysql. |
15 |
> >>> |
16 |
> >>> Someone was looking at postgresql as an alternative to mysql, but I'm |
17 |
> >> |
18 |
> >> not sure |
19 |
> >> |
20 |
> >>> that this would bring any benefit. |
21 |
> >> |
22 |
> >> pg is a fine database, but for this use will always be a 2nd class |
23 |
> >> citizen. Most users will already have mysql installed, or will be |
24 |
> >> willing to install it. |
25 |
> >> |
26 |
> >> The number of folks with pg and without mysql will probably be small |
27 |
> > |
28 |
> > Not necessarily. |
29 |
> > People who care about databases actually supporting SQL properly and |
30 |
> > performing properly will prefer PostgreSQL. |
31 |
> > |
32 |
> > I don't like to be forced to run a MySQL instance as well. It's often the |
33 |
> > laziness of developers that causes the difficulty of supporting a |
34 |
> > different database when they started with MySQL. If you start with a |
35 |
> > different one, like PostgrSQL, supporting different database engines is |
36 |
> > very simple. |
37 |
> |
38 |
> I don't think you read what I said. |
39 |
|
40 |
Sorry, didn't read the below in what you put. |
41 |
|
42 |
> I didn't say postgresql shouldn't be supported, I said it would always |
43 |
> end up being a second class citizen as the number of people who'd be |
44 |
> happy with mysql will vastly outnumber the number of people who highly |
45 |
> desire postgresql. So, logically, a postgresql driver in this case will |
46 |
> probably just bitrot away. Whihc nicely explains the likely reason why |
47 |
> that driver is not there. |
48 |
|
49 |
It wouldn't bitrot away as there would be people willing to keep it working, |
50 |
provided it wouldn't require a MySQL -> SQL translator to be kept up-to-date. |
51 |
|
52 |
> People like yourself who care about databases are very much in the |
53 |
> minority of users, even on Linux. Most users across the boards just |
54 |
> don't give a shit. Them's the breaks. |
55 |
|
56 |
Users never care about what they install. I just wish the majority of |
57 |
developers would actually be willing to follow some simple guidelines to make |
58 |
it actually possible to others to write and maintain the drivers to connect to |
59 |
different databases. |
60 |
|
61 |
Several attempts have been made by people to add support for different |
62 |
databases to various projects. I've tried to do it myself on occasion, but |
63 |
even when patches are accepted by upstream, they get broken by upstream at a |
64 |
future release again because of the bad design that is often employed by lazy |
65 |
developers. |
66 |
|
67 |
-- |
68 |
Joost |