Mixxx overwrites database file without warning when importing mixxxtrack.xml

[Sean M. Pappalardo]

Mixxx should pop a warning asking to overwrite or not if there's already a database file when it attempts to create one during import.

[Albert Santoni (gamegod)]

It doesn't overwrite the database, it'll just import the tracks if they aren't in the DB.

Why is this a problem?

[RJ Skerry-Ryan (rryan)]

I think he means it renames the Mixxx 1.7.x database as mixxxtracks.xml.old every time you run Mixxx 1.8.0. This might be an issue if someone wants to switch off between Mixxx 1.8.0 and Mixxx 1.7.2.

[Albert Santoni (gamegod)]

Ok, how do you want to deal with users that want to switch back and forth then?

I just feel like it's not worth our time to support moving backwards
to older versions of Mixxx. 1.8 won't be _that_ bad, right? :)

Albert

On Sat, Jan 30, 2010 at 3:10 PM, RJ Ryan <email address hidden> wrote:
> I think he means it renames the Mixxx 1.7.x database as
> mixxxtracks.xml.old every time you run Mixxx 1.8.0. This might be an
> issue if someone wants to switch off between Mixxx 1.8.0 and Mixxx
> 1.7.2.
>
> --
> Mixxx overwrites database file without warning when importing mixxxtrack.xml
> https://bugs.launchpad.net/bugs/514540
> You received this bug notification because you are a member of Mixxx
> Development Team, which is subscribed to Mixxx.
>

[Sean M. Pappalardo (pegasus-renegadetech)]

Oh, no, I didn't know that the importer was merging into the existing DB. (Didn't give you guys enough credit!) However, does the importer clobber tracks in the DB with imported ones with the same name? Even if so, that's not really a bug...maybe it should ask in case of conflict.

[RJ Skerry-Ryan (rryan)]

I don't believe so -- if the track exists it does nothing.

On Thu, Feb 11, 2010 at 6:28 AM, Pegasus <email address hidden> wrote:

> Oh, no, I didn't know that the importer was merging into the existing
> DB. (Didn't give you guys enough credit!) However, does the importer
> clobber tracks in the DB with imported ones with the same name? Even if
> so, that's not really a bug...maybe it should ask in case of conflict.
>
> ** Changed in: mixxx
> Status: Confirmed => Incomplete
>
> ** Changed in: mixxx
> Assignee: Pegasus (pegasus-renegadetech) => (unassigned)
>
> --
> Mixxx overwrites database file without warning when importing
> mixxxtrack.xml
> https://bugs.launchpad.net/bugs/514540
> You received this bug notification because you are subscribed to Mixxx.
>

[Phillip Whelan (pwhelan)]

  I've seen some of my old databases pile up several duplicate entries
while testing out 1.7 and trunk on the same computer. I cannot
confirm why though.

[Albert Santoni (gamegod)]

On Thu, Feb 11, 2010 at 8:24 AM, RJ Ryan <email address hidden> wrote:
> I don't believe so -- if the track exists it does nothing.
>

Correct!

Thanks,
Albert

> On Thu, Feb 11, 2010 at 6:28 AM, Pegasus <email address hidden>
> wrote:
>
>> Oh, no, I didn't know that the importer was merging into the existing
>> DB. (Didn't give you guys enough credit!) However, does the importer
>> clobber tracks in the DB with imported ones with the same name? Even if
>> so, that's not really a bug...maybe it should ask in case of conflict.
>>
>> ** Changed in: mixxx
>>       Status: Confirmed => Incomplete
>>
>> ** Changed in: mixxx
>>     Assignee: Pegasus (pegasus-renegadetech) => (unassigned)
>>
>> --
>> Mixxx overwrites database file without warning when importing
>> mixxxtrack.xml
>> https://bugs.launchpad.net/bugs/514540
>> You received this bug notification because you are subscribed to Mixxx.
>>
>
> --
> Mixxx overwrites database file without warning when importing mixxxtrack.xml
> https://bugs.launchpad.net/bugs/514540
> You received this bug notification because you are a member of Mixxx
> Development Team, which is subscribed to Mixxx.
>

[Sean M. Pappalardo (pegasus-renegadetech)]

Marking invalid

[Swiftb0y (swiftb0y)]

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/5297