1 |
On 12/08/2014 21:00, J. Roeleveld wrote: |
2 |
> On 12 August 2014 20:21:03 CEST, Volker Armin Hemmann <volkerarmin@××××××××××.com> wrote: |
3 |
>> Am 12.08.2014 um 16:10 schrieb J. Roeleveld: |
4 |
>>> On Tuesday, August 12, 2014 03:38:15 PM Alan McKinnon wrote: |
5 |
>>>> On 12/08/2014 15:28, J. Roeleveld wrote: |
6 |
>>>>> On 12 August 2014 14:06:07 CEST, Alan McKinnon |
7 |
>> <alan.mckinnon@×××××.com> |
8 |
>>> wrote: |
9 |
>>>>>> On 12/08/2014 11:10, Mick wrote: |
10 |
>>>>>>> I recall the devs explicitly stating early enough in the KDE4 |
11 |
>>>>>> development that |
12 |
>>>>>> |
13 |
>>>>>>> sqlite is not man enough for the job and advising everyone to |
14 |
>> move |
15 |
>>>>>> over to |
16 |
>>>>>> |
17 |
>>>>>>> mysql. |
18 |
>>>>>>> |
19 |
>>>>>>> Someone was looking at postgresql as an alternative to mysql, but |
20 |
>> I'm |
21 |
>>>>>> not sure |
22 |
>>>>>> |
23 |
>>>>>>> that this would bring any benefit. |
24 |
>>>>>> pg is a fine database, but for this use will always be a 2nd class |
25 |
>>>>>> citizen. Most users will already have mysql installed, or will be |
26 |
>>>>>> willing to install it. |
27 |
>>>>>> |
28 |
>>>>>> The number of folks with pg and without mysql will probably be |
29 |
>> small |
30 |
>>>>> Not necessarily. |
31 |
>>>>> People who care about databases actually supporting SQL properly |
32 |
>> and |
33 |
>>>>> performing properly will prefer PostgreSQL. |
34 |
>>>>> |
35 |
>>>>> I don't like to be forced to run a MySQL instance as well. It's |
36 |
>> often the |
37 |
>>>>> laziness of developers that causes the difficulty of supporting a |
38 |
>>>>> different database when they started with MySQL. If you start with |
39 |
>> a |
40 |
>>>>> different one, like PostgrSQL, supporting different database |
41 |
>> engines is |
42 |
>>>>> very simple. |
43 |
>>>> I don't think you read what I said. |
44 |
>>> Sorry, didn't read the below in what you put. |
45 |
>>> |
46 |
>>>> I didn't say postgresql shouldn't be supported, I said it would |
47 |
>> always |
48 |
>>>> end up being a second class citizen as the number of people who'd be |
49 |
>>>> happy with mysql will vastly outnumber the number of people who |
50 |
>> highly |
51 |
>>>> desire postgresql. So, logically, a postgresql driver in this case |
52 |
>> will |
53 |
>>>> probably just bitrot away. Whihc nicely explains the likely reason |
54 |
>> why |
55 |
>>>> that driver is not there. |
56 |
>>> It wouldn't bitrot away as there would be people willing to keep it |
57 |
>> working, |
58 |
>>> provided it wouldn't require a MySQL -> SQL translator to be kept |
59 |
>> up-to-date. |
60 |
>>> |
61 |
>>>> People like yourself who care about databases are very much in the |
62 |
>>>> minority of users, even on Linux. Most users across the boards just |
63 |
>>>> don't give a shit. Them's the breaks. |
64 |
>>> Users never care about what they install. I just wish the majority of |
65 |
>> |
66 |
>>> developers would actually be willing to follow some simple guidelines |
67 |
>> to make |
68 |
>>> it actually possible to others to write and maintain the drivers to |
69 |
>> connect to |
70 |
>>> different databases. |
71 |
>>> |
72 |
>>> Several attempts have been made by people to add support for |
73 |
>> different |
74 |
>>> databases to various projects. I've tried to do it myself on |
75 |
>> occasion, but |
76 |
>>> even when patches are accepted by upstream, they get broken by |
77 |
>> upstream at a |
78 |
>>> future release again because of the bad design that is often employed |
79 |
>> by lazy |
80 |
>>> developers. |
81 |
>>> |
82 |
>>> -- |
83 |
>>> Joost |
84 |
>>> |
85 |
>>> |
86 |
>> wasn't qtsql once supposed to that? |
87 |
> |
88 |
> If a framework like qtsql is used, swapping the database is easy. |
89 |
> |
90 |
> Most developers seem to prefer to reinvent the wheel and often come up with something that vaguely resembles a circle and is held together with a mixture of glue and duck tape. |
91 |
|
92 |
|
93 |
I blame php and others of it's ilk. |
94 |
|
95 |
The good thing about php is that everyone and their dog can knock out |
96 |
running code. |
97 |
The bad thing about php is that they do. |
98 |
|
99 |
Substitute mysql and bash if you will and tweak the content to suit - it |
100 |
all works out the same. |
101 |
|
102 |
Sensible languages (like, oh I dunno - python maybe?) have this trick |
103 |
about them - you have to work hard to write awful code. You also have to |
104 |
work hard to write awesome code, but if you just follow the book you |
105 |
usually end up with acceptable code. |
106 |
|
107 |
I will refrain from commenting on perl. |
108 |
|
109 |
|
110 |
-- |
111 |
Alan McKinnon |
112 |
alan.mckinnon@×××××.com |