Status of mysqle

[Casey Link]

On Wed, Aug 27, 2008 at 12:25 PM, Leo Franchi <lfranchi at kde.org> wrote:
>
> On Aug 27, 2008, at 11:19 AM, Mark Kretschmann wrote:
>
>> On 8/27/08, Lydia Pintscher <lydia.pintscher at gmail.com> wrote:
>>> On Wed, Aug 27, 2008 at 14:34, Dan Meltzer <parallelgrapefruit at gmail.com
>>> > wrote:
>>>> On Wed, Aug 27, 2008 at 8:32 AM, Jeff Mitchell
>>>> <kde-dev at emailgoeshere.com> wrote:
>>>>> Anyone know the current status?  If we're ever going to use mysqle
>>>>> instead of sqlite, we should be doing so before 2.0 hits, or it
>>>>> will be
>>>>> quite difficult to change later.
>>>>
>>>> It would be a very bad idea to change now, with us getting well into
>>>> the beta cycle.  We should stick with what we know works for 2.0.
>>>
>>> I agree. Changing it now is meh :/
>>> Edward was looking into it all but he seems to be MIA :(
>>> I hope he returns sooner rather than later.
>>>
>>> I think we have no choice but to delay it at least until 2.1. Sucks.
>>> Other opinions?
>>
>> I agree as well.
>
> At this point, i think we really have no other option. We can;t
> introduce such a massive change as that between betas....
>

As long as the change comes soon-ish. Users with large collections (me
included) suffer greatly when forced to use sqllite.

Also, there is another feature regresion that I haven't seen mentioned
yet. With 2.0 users won't be able to share their collections across
multiple computers while keeping their collection database on one
machine. And the answer to this isn't "Use ampache", because (1)
Ampache is much more overhead (php, httpd, etc), (2) the Ampache
service isn't a fully supported collection in terms of the Query
Maker. That is, Ampache tracks can't be used universally in playlists,
dynamic playlists, etc.

Casey