Does "import" have a bug?

[Pacerier]

I exported 10k notes as xml. It's completed pretty quickly.

Then I imported them into a brand new Cintanotes. In a pretty short time, I see it at 100%:



But after that, it has been stuck on this screen like this for the past hour.

Is this a bug?

Or should I continue waiting?

[Pacerier]

Ok ignore this. It finally ended importing.

[CintaNotes Developer]

It probably was stuck checking for duplicates. If there are a lot of similar notes, it can be an issue.
If you check the "Allow duplicates" checkbox, the import will go much faster.

[Pacerier]

Ic, it's working.

Suggestion: should have some kind of warning or put it as the default, or at least a progress bar that shows the progress of duplicate checking. and duplicates should be real duplicates. byte-for-byte same data and meta data. Two pieces of notes with the same title yet different time should be recognized as two distinct notes.

[CintaNotes Developer]

We'll try to improve the process for sure.

Re. checking for duplicates: not only note title is checked, but all other fields as well.
I can't see how it could be useful to have two exact same notes differing only by modification date?

[Pacerier]

I'm using each note as a row in a database.

For users that do this, they too will need creation date to be recognized as a unique info.

Eg, I store row1:

data: ABC, created-date: D1.

Then, somewhere down the road, I store row2:

data: ABC, created-date: D2.

Then, somewhere down the road, I store row3:

data: ABC, created-date: D3.

The database should look like this:
data: ABC, created-date: D1.
data: ABC, created-date: D2.
data: ABC, created-date: D3.

It's 3 unique rows! You can't just collapse them into one row.

[CintaNotes Developer]

There's just one question here: why exactly are you expecting from a note-taking program functionality of a general-purpose database and want to impose your semantic over semantic that's built in to the program?