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