Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - Anson

Pages: [1]
1
Feature Suggestions / options for booleans in CSV files
« on: October 13, 2009, 06:12:27 am »

from a recent thread and some past similar ones, I got an idea for some future improvements which will probably go somewhere in the lower parts of any todo list only, but which still might be nice :-)


the first idea is about small changes to the default CSV export templates

Quote from: rick.ca on August 08, 2009, 11:54:11 am
To output boolean fields like viewed and bookmarked, include the line boolvals="yes<->no" in the options section of the template.

it is nice to be able to set the strings for output which are used for true and false. but to make templates work even if people forget (or don't know) to set this line, could this line be included by default in the templates ? It probably shouldn't be much work to do, and also wouldn't hurt if not needed ...

I also have seen that some templates have a delimiter at the end of lines. is that really needed for PVD's CSV files? usually the delimiter is not really a delimiter of all fields, but only a separator between fields, and adding a delimiter at the end causes an additional field (with empty value) to be added as last field of the record.


a second nice (more difficult to implement and also not very important) feature might be to do on purpose what someone falsly has done: setting the strings for true and false for a specific field instead of having only one definition for all booleans in a CSV file. the definition in the options section still would serve as default for those fields without their own definition.

currently, i have to use (among other options)
Code: [Select]
%OPTIONS%
boolvals="true<->false"
%OPTIONS%
%HEAD%onebool;anotherbool;defaultbool
%HEAD%{%value=wish};{%value=viewed};{%value=mybool custom="true"}to generate something like
Code: [Select]
onebool;anotherbool;defaultbool
false;true;true
true;true;false
false;false;true

the changed syntax would allow for something like
Code: [Select]
%OPTIONS%
boolvals="yes<->no"
%OPTIONS%
%HEAD%onebool;anotherbool;defaultbool
%HEAD%{%value=wish boolvals="wish<->owned"};{%value=viewed boolvals="seen<->tosee"};{%value=mybool custom="true"}to generate something like
Code: [Select]
onebool;anotherbool;defaultbool
owned;seen;yes
wish;seen;no
owned;tosee;yes


btw: which values are accepted as booleans by the CSV import plugin?
true/false, yes/no, 1/0, something else ?
making this also selectable probably would be overkill and pure SciFi :-)
(and thus also setting own values for different fields is even less important)

2
Support / two problems with CSV-files
« on: October 12, 2009, 02:27:41 am »

I wanted to import and export info with CSV-files, and while doing so, stumbled upon two problems. Further testing finally gave me the reasons what probably happened, but now i am looking for methods what to do ...


problem 1:
i had written a program to read a CSV file and work on the values in it, but it behaved strangely. Looking at the contents of the CSV showed nothing special, but finally i looked at every byte with my own program, and thus i found that in front of the first character were three more chars with the codes 239, 187 and 191. Notepad simply seems to ignore them, but other software might not.

when i had a closer look at the original CSV export template in PVD v14, I saw this:
Code: [Select]
%OPTIONS%
encoding="UTF8BOM"
replace=";<->,"
replace=""<->"
replace="#13#10<-> "
replace="#13<-> "
replace="#10<-> "
filter="CSV Files|*.csv"
%OPTIONS%
%HEAD%Title;Original Title;Year;Genre;Country;Actors;Director;Description;
%HEAD%{%value=title};{%value=origtitle};{%value=year};{%value=genre};{%value=country};{%value=actors};{%value=directors};"{%value=description}";
and that already was the solution to removing the three extra chars: i changed encoding="UTF8BOM" to encoding="UTF8" (without BOM) and everything works fine now.

now the questions:
  • Was the change to UTF8BOM intended ? in other/older versions and forum posts, i only had seen UTF8 and UTF-8 (which of the two is correct?), but never saw UTF8BOM ?
  • which encodings should be used to make CSV-files as compatible to as many other software as possible ?
  • and which encodings are available at all (does this depend on PVD or my system) ?


problem 2:
after importing my collection via CSV without obvious problems, i had to see that there was one problem: many comments were truncated in the middle. a closer look revealed that that happened always at some quotation marks which occured in the middle of a field.

Now the reason for the problem is obvious: PVD only imports fields "as is", respecting the userdefined delimiter and the userdefined quotation character, but only by ignoring the first and second occurence of the quotation character and the remaining string after the second quote char (assuming they enclose the field at the start and end of the field), but PVD does not interpret doubled quotation marks which are used by many other programs and even listed in a RFC.

This is no bug since the RFC and other sources give a warning: "While there are various specifications and implementations for the CSV format, there is no formal specification in existence, which allows for a wide variety of interpretations of CSV files.". Nonetheless, it would be nice if a future version of PVD would also understand those additional conventions.

Similar also applies to exporting to a CSV file: in the options section all characters which might cause problems are replaced, eg quotes are simply removed, linebreaks are replaced by space, and semicolons are replaced by commas. I found that problematic since it messes up lots of my comments, and nice features of PVD like the imbedded hyperlinks in memo fields don't work any longer when exporting and reimporting them since they will be missing the quote chars. Most serious will be the rare cases where a title is changed because it contains the delimiter or the quote char, since title and year are used to identify a movie.

now the questions:
  • would other people also be interested in more fully using import and export of CSV-files, or do most people use excel import because of this (but as i understood, exporting to excel is done with the same "normal" CSV-files and thus also the related problems) ?
  • did someone already come up with suggestions or even a solution how to change a few parameters to be able to import and export everything with as little loss as possible ?


here are some links for reference: Wikipedia and RFC 4180

and a short summary of these sources what most implementations understand:
  • fields of one record are on one line and are separated by one specific delimiter (originally "," but now often ";" since there are lots of "," and much fewer ";" in strings and most of all in numbers)
  • the delimiter separates values and doesn't terminate them (thus no delimiter is required after the last field; a final delimiter would add an empty field to the line/record)
  • any field may be enclosed with specific quotation characters
  • if a field contains the delimiter, the quotation char or linebreaks, it must be enclosed in those quote chars, and quote chars in the field are doubled to escape them
  • depending on implementation, whitespace at the start and end of fields should not be trimmed (to be sure, the whole field can be enclosed in quote chars)
  • a single header line is optional, but if present should hold the same number of fields as all the other lines, and the values should be the names of the fields

my first idea for a temporary solution for export only: changing the replace command in the options section to double quote chars instead of removing them and to no longer change ";" into "," and no longer remove linebreaks, and putting quote chars around all fields in the body of the template, or at least around all fields which at some time might include the delimiter or the quote chars, including titles, original titles, and all other strings and memo fields. this might work, but only as long as the data is not intended for reimport.

my first idea for a temporary solution for import and export: using a delimiter which is guaranteed to appear in no fields like maybe a TAB or other nonprintable char (if such chars are possible at all), but maybe someone uses TAB in comment fields. thus which char to use ? with a carefully selected delimiter, maybe quote chars wouldn't be needed at all and thus require no measures (except removing the replace commands in the header). And which second special char could be used as quote char, eg to avoid misinterpretations by PVD and other software when such software should attempt to match a userdefined quote char, which (when empty) might match any place in a string.

would anyone be interested in exploring this further, or even does have some working solution ?

3
Feature Suggestions / referring to old "lots of suggestions"
« on: October 07, 2009, 01:01:53 pm »

This post is support referring to old "lots of suggestions" from summer 2008:

Quote from: Dadeo on June 10, 2008, 07:48:12 am
Quote from: rick.ca on June 10, 2008, 08:17:46 pm
Quote from: nostra on June 11, 2008, 12:46:10 pm

Quote
  • 2. TV Series Season Data - is it possible to have a record for each Season?
  • 2. This would be nice. ... And there are situations when the only complete information available is for a whole season.
  • 2. Already in my TODO list

I will find this feature most useful for next Xmas, to keep track of which season boxes I already have, which season boxes to put on wish lists for relatives, where i will store the new DVDs from them, etc.

I could simply duplicate the main season record and edit the original title and/or localized titles to include the season, but that would result either in problems with duplicates eg on "compact database", or i wouldn't be able to download and update episode data easily (title(year) wouldn't be correct any longer, and it would require lots of manual work afterwards).

Quote
  • 6. Find/Replace, Global Changes - Could there be some way to make global changes to data?
  • 6. There is a Multiple Movies Editor—just select multiple items (movies or episodes) before selecting Edit.
  • 6. There is already a Multiple movies editor as rick said, you can also change list values for all records in Tools -> Preferences -> Lists

At first sight, the Multiple Movies Editor looks very nice, but it includes few fields only, and most of all it includes none of my custom fields.

thanks for this hint, i had forgotten that i once saw the rename option; but:
The editing options in Tools -> Preferences -> Lists look nice too, but also there, my custom select fields are not included

just tested: renaming a list value not only renames the value but also merges it with another identical value, just like it should be when the set of values is intended to be a unique list of values. The advantage is that correcting "disney" to look like "Disney" would not create two values of "Disney".
But there is no warning when accidentally renaming a value to another existing value, immediately and quietly merging the two and making it impossible to undo later since the distiction between the two is lost. Currently it also is not possible to rename/merge more than a single value at the same time without getting a database error about requiring unique keys.

Quote from: rick.ca on June 12, 2008, 11:48:08 pm
If Multiple Movie Edit doesn't help (because it doesn't include the field you need to change), consider preparing an import file with just the corrected information (i.e., title, year, corrected data) and import that. I'm not sure this works for just deleting unwanted data—a null import field may be ignored, leaving the unwanted data intact.

Best method to do such and any other larger changes and/or merges of list values might be to export and reimport data, which leads to the next point:

Quote
  • 8. Import/Export - ... I find it cumbersome to have to go to Preferences every time. Also, when selecting fields I would love a button to select/deselect all fields, and the ability to double click a field and have it added to/removed from the list.  When Importing it would be so helpful to have PDB read the header line of the file to make it easier for mapping fields.
  • 8. I agree, having to configure an export template is a pain; it would be nice (and less error-prone) it there were at least a way select from available fields. Also, it would be nice if import configuration took a shot at automatically matching import fields to existing fields, then let the user modify the mapping.
  • 8. I will consider improving export/import configuration

As soon as people understand how to select the fields for CSV-import, there should be no big problems except that depending on the intended purpose, all fields have to be cleared and set up differently each time. For the export, setting up different combinations of fields is even more trouble and thus it would be nice to have almost exactly the same dialog as for import, simply selecting fields from a list and selecting the characters for delimiter and text qualifier. The export function then would be able to write a proper header, and also to automatically convert values if needed (putting text qualifiers around strings which include the delimiter or CRLF, doubling the text qualifiers inside those strings, etc)
I believe that those conversion problems currently are solved only by simply replacing the problematic chars in the options of the export template and thus not allowing for text qualifiers, delimiters or CRLF to be included in exported values at all ?

When export and import are done to modify some values and reimport them later, the feature of automatically matching fieldnames in the header would be very helpful: export writes them, and import could use them with 100% accuracy. As a safeguard or when some headerfields don't match, the recognized fields could at least be used as a default to start matching the fields in the current dialog.


To use this export/edit/reimport (which rick suggested above) for all cases, other features would have to be added too, so that an exported and edited list of CSV-records will be read correctly to update exactly the records which were exported and no other records with the same title or title(year), and also so that it can be used to change the title or year of existing records.
But even if not for all cases, the above improvements to export (easier field selection and no more or at least easier templates) and import (automatic field selection) would be huge improvements.

4
Scripts and Templates / Exporting Episodes to CSV
« on: October 02, 2009, 09:48:03 am »
- it would be nice if some basic data which is required to identify an episode and additional modified data could be exported by such a template, eg series title, episode season and number, episode title, and in addition (localized) title, flags for wish and seen, and maybe a file path.

- really useful would be such an export if there would be also a corresponding import that allowed for updating the (localized) title, flags and a file path after getting the series data with a plugin (eg from IMDB; eg for creating a new partial database or just to recreate everything if i do a "readable" backup to a CSV file), but probably any import which can currently be done would be for "main entries" only and not for episodes, is this correct?

5
Support / small problems with alphabetical sorting and with autocompletion
« on: October 02, 2009, 06:56:04 am »

problem with alphabetical sorting

When the list of movies, actors or some grouped listing are sorted, it is done strictly according to the charset (ASCII?). This results in listing all uppercase titles first, followed by lowercase titles. While people use the complete titles without moving "The" to the end of it, and while using english titles (usually all words are capitalized), this doesn't matter much, but when there are lots of German (or french, italian, etc) titles, and/or when moving articles to the end, many titles suddenly appear at the end of the movielist instead of being alphabetically sorted together with the capitalized words. Similar also applies to special characters like "-", "'", "(", etc, and also to special local characters like äöüÄÖÜß, èéêùúû, etc which partially appear before uppercase, between upper and lowercase, and after lowercase.

It would be nice to be able (either by default or selectable by an option) to sort all special chars together at one place (either before or after all other chars), and most of all to sort chars according to the local language or in some other merged way, at least ignoring upper and lowercase, or even eg AaÀàÁáÄä together, followed by Bb, etc


problem with autocompletion

In my database, I have added several custom items, including "select list". When I want to select a value in such a list by typing the first few chars, two effects occur:

The chars i type are taken literally including uppercase and lowercase, and autocompletion only takes the rest of the string from the selection list. Since the typed chars are taken as typed but it looks as if the field was automatically filled with an existing value, I already ended up several times in unintentionally creating a new value which I couldn't easily see (because of the sorting problem, see above).
Example: A value "Disney" already exists in the selection list, but i simply type "d". Autocompletion makes "disney" from it, and when i accept, a new value is created. Sorting or grouping by this field will later cause this new value to show up at the end behind all uppercase values (A ... Disney ... Z ... disney) and the record seems to be missing in the database when i look at the "Disney" group.
It would be nice when case would also be adjusted automatically, although i recognize the problem of "how to add a new value starting with different case if a value starting with those letters already exists"
I have no perfect solution for it, but wanted to explain the small problem i have with the current situation. Maybe in the meantime, autocompletion could match the exact case only, which would require a little more carefulness (also using the shiftkey instead of "just typing"), but avoid unintentional additional values.

Another problem with autocompletion is a bit more strange:
In a custom select list, i have (amongst others) the values "Horror - King", "Stephen King", and "King Kong". And here is what the autocompletion does:
- on typing "step", I get "stephen King"
- on typing "horr", I get "horror - King"
   (both as expected, with lowercase problem: see above)
- on typing "stephen ", I get "stephen "
- on typing "horror ", I get "horror "
   (both: why is the rest no longer completed when i type the space?)
- on typing "stephen ki", I get "stephen king Kong"
   (rest is completed again, but: what kind of completion is THAT?)
   (at least i had a good laugh on Stephen's new nickname :-)
- on typing "horror - ki", I get "horror - ki"
   (rest still is no longer completed after i type space and "-",
   and it is also not even completed as above like "horror - king Kong")

Is the autocompletion done by PVD by doing some patternmatching, and the regex and stringoperations cause also unintentional matches like the "Stephen King Kong"? When i programmed something with a listbox in one of my programs, i set flags to ignore case and to alphabetically sort the list. When I type something in the editfield of that dropdownlist now, it doesn't show autocompletion, but opening the pulldown or using wheel or cursorkeys shows the first value which matches these typed chars, making it easy to use mousewheel or cursor-up/down to select an existing value (including the correct case of the characters), and the preselection of a value speeds up scrolling to the intended value, most importantly in very long lists.
Of course, this is only my personal approach in one of my programs, but for my style of working, it worked out: type a few chars (without watching for correct case), use the wheel or cursor (even a single "down" will do), and get to a correctly spelled existing value fast. For these abilities and less other problems, i would gladly sacrifice a shown autocompletion :-)


ps: another small general problem with the select lists is that after editing a record, typing a new value for a select list, and applying the changes, this value won't be considered for autocompletion on editing another record later, unless i have first clicked the arrow to pulldown the selection list at least once: The list of values seems to not be updated automatically, and i have to force such an update by showing the list manually once.

6
Support / another case of "movie already might exist"
« on: October 01, 2009, 09:35:48 pm »
Although we already talked a lot about uniqueness and the difficulties associated with it, here is just another case of "movie already might exist" which IMHO shouldn't have happened at all, and if it happened it should have dealt with a bit differently.

In my database, there are "several" movies with identical names and some of them even identical years (those are the movies which get a suffix to the year in the IMDB, like yyyy/I, yyyy/II, etc), but they all have different additional fields like a unique ID, different unique URL, several different custom fields, etc.

When I just tried to edit one such movie with a duplicate "otitle (year)" and only changed its title (localized version of the title, but otitle and year unchanged), i got that dialog once again that the title might already be existing (of course it should, since i was editing an existing movie!) and whether i wanted to add a new movie or use the existing otitle (year). The dialog only gave me two options in the list: "add" and one single movie (which one was it, the edited movie or the other?). But that was not confusing enough: the only info that the dialog gave was the name and the year (which of course are not unique and thus not good enough in this case) and the ID field was empty.
Although one might differ on everything else, at least the ID should be given since both records had an ID before editing and the edited record still had its old ID. And if you can never provide the ID in that dialog (i can't remember ever seeing an ID in that dialog), the empty ID field shouldn't appear in the dialog.
btw: what use does the ID field have anyway, if it is not used to identify a record (eg when importing an updated series of movies from CSV files)

Please improve on that "duplicate detection" feature, eg:
- don't ask which movie to update (merge?) when i edit a specific movie record and ask only when i create a new record
- fill out also the ID of the movie in that dialog and maybe give additional info to identify them
- and in general (for some future version), give some option to use additional fields like ID or URL to detect uniqueness automatically

some statistical background for the first 3000 records i imported:
- 35 records (more than 1%) with non-unique "otitle (year)" data which gets that /I /II suffix in IMDB
- from 4 of those 35, I have both versions in the database
- almost 100 non-unique "otitle"
- those 100 otitles result in something like 270 records with non-unique "otitle" (9% of the records in my database) which mostly would be unique by using year and type (series/movie) and only 3 or 4 would need additional info like /I /II
- ALL of those records would be unique when URL or ID fields would be considered
no wonder that i get lots of trouble with PVD asking me for verification of duplicates

ps: as Movie Information Skin I use "PVD Classic". It would be nice if i wouldn't have to edit the skin myself for every update to accomodate for IDs with more than only 4 digits (for visible records, I use the 7-digit IDs from the IMDB URL, and for invisible automatically generated records i let PVD assign IDs of 10000000+, but also many other people probably have more than 9999 records in the database).
Can you please make that field a bit larger as default and/or autoadjust to larger IDs ?

7
Support / two BUGS with SQL queries
« on: September 21, 2009, 10:04:11 am »
first bug, in advanced search:
I had defined several custom items, among them some "Select List" and some "Multiselect List".
When i try to do an advanced search "(loc1 IS NOT NULL) and (loc2 IS NOT NULL)", i get the following errorbox:
Code: [Select]
Dynamic SQL Error
SQL error code = -204
alias MOVIES CUSTOMSHORT154601265 conflicts with an alias in the same statement
Undefined name
Error Code: 249
To eliminate possible side effects from my database, upgrading the version, etc, I did the same test again with a fresh (newly created) database in v14, first adding only one field of both types, and then doing an advanced search on the empty database with the same advanced query "(loc1 IS NOT NULL) and (loc2 IS NOT NULL)". The result was the same errorbox as above (except for a different name "CUSTOMSHORT155341073")

more tests:
- changing the condition (IS NULL, = "x", contains "y") resulted in the same error.
- doing the tests with two "Select List" results in no error.
- doing the tests with two "Multiselect List" results in no error.
- changing the order "(loc2 ...) and (loc1 ...)" gives the same error again.

second bug, in displaying a grouped listing:
after i started PVD again and opened my normal database, the old grouping (context menu "group as") was lost and instead the standard grouping was used (is that a feature or a minor bug too; it would be nice if such settings would be saved and restored for each database and between PVD sessions).

The standard grouping is according to the original title's first letter, and everything seemed to be nicely grouped, including movies which start with digits and also some special chars. I could expand (click on the little "+" sign to the left of the group) groups which start with a dot (http://www.imdb.com/title/tt0068154/ in case someone needs such a title for testing himself), a minus, an asterisk (http://www.imdb.com/title/tt0092494/), but when I want to expand the group which has single apostrophes ("'", like in http://www.imdb.com/title/tt0306872/), I get an SQL error:
Code: [Select]
InitChildren
Dynamic SQL Error
SQL error code = -104
Unexpected end of command - line 1, column 376
Invalid token
Error Code: 249
when I did the same again now (a few hours later), i get no such errormessage, but the rest stays the same: the "+" in front of the folder symbol disappears, the folder symbol stays the same (with a green plus sign on it) and no details/movies from the group are listed.

8
Support / Re: Deleting from People View - according to Anson
« on: September 18, 2009, 01:02:40 am »
Quote from: rick.ca on September 17, 2009, 07:30:42 pm
Deleting people doesn't just make them invisible, it actually deletes the record.

NO: I just tested it on a new database with v0.9.9.13, and besides a problem with refresh not working automatically, it worked as expected, if i remember exactly which state the entries have (invisible entries shown, or having really visible entries):

- adding two movies only shows grey actors in the people list since i don't auto-download people's info, and only one or both of the movies are shown for them. To see the actors, i have set the filter to show all people including grey invisible actors.
- when i delete one such grey actor, the record is removed completely since it is already an invisible record.

- downloading people's info with a plugin causes the data to be loaded, but the actor still looks grey in the list until i manually refresh the list with F5 (this is at least a feature, if not a real (small, minor) bug). then the actor is shown with white background and appears also when resetting the filters to normal (only visible shown)
- (before the next step, i have set the filters back to also show invisible records)
- pushing the DEL key with one of these white actors selected first asks me the security question (with the hint to hold CTRL to completely delete the record), and then the actor is removed from the list of actors, but only until I refresh the list again with F5 (same as above: feature or bug, that i have to manually refresh?). After using F5, the actor is shown to be back on the list as grey entry, and thus it was NOT deleted completely. This is exactly what should happen {edit:} except for the fact that now even the invisible record still has all the info and not only info for the two movies like at the beginning when the actors were added invisibly with only visible movies being listed.

lessons from the above tests:
- use F5 often
- if you don't autodownload actor's info, records for people are invisible (you can see them, but only if the filter is set to show invisible records), and deleting them deletes them completely
- if an actor is visible (because of autodownload or manual update), deleting it behaves like deleting visible movies: it only makes it invisible unless CTRL is held down too.
- the actor's record will never be the same minimal record again like in the beginning, unless it is deleted completely together with many movies, and movie info for all related movies is downloaded again (see also the warning in the preferences: "these changes can not be undone easily")


Quote
This doesn't surprise me, as normally there are no "invisible" people.

hehe, see http://www.imdb.com/title/tt0220238/ :-)

more serious: there are also no invisible movies which you can see. But you probably autodownload all people's data when importing a movie, and THEN, there really never are "invisible" records in people view.


Quote
If a person is no longer associated with any visible movies, then it would be logical to make them invisible.

Sounds nice, but would raise another problem: users should be allowed to have actors even if none of their pictures are currently visible, eg because i just started to add movies by following a filmography (first step: create actor, second step: download actor, third and fourth steps: follow links in filmography and download movies; alternate third step when following your above logic: make the actor invisible, removing his filmography, before being able to follow links from the filmography to download movies).

Quote
Conversely, if the user "deletes" a person who is still associated with visible movies, then the record should be make invisible, not actually deleted. Deleting people should be a way of stripping a record of all the information from the record, except for the links to existing visible movies. In other words, the same behaviour as for deleting movies.

According to my tests above, it seems to be done just like you suggest.

Quote
To fix the situation where a person has been accidentally deleted, update the movie they were previously associated with. Then update the person's record as well—that will restore them to any other movies they might have been associated with.

might work ... but depending on your method to work with people (I almost never download info for people), maybe the actor would have to be deleted again (with DEL, and NOT with CTRL+DEL) to make him invisible again, and even that would still leave lots of info in the invisible record.

9
Support / Adding movies, etc.
« on: September 10, 2009, 02:25:14 am »
Quote from: nostra on September 09, 2009, 07:20:28 pm
isntall the latest update 0.9.9.13!

yes, thanks to your fast actions.
a few hours ago it was still 12 and that version wasn't very old either yesterday :-)

I now have installed the new version 0.9.9.13 and on a new database, I no longer get conversion errors when I add movies.

But when one problem is solved in any software, i always find two others :-)
eg that I have to manually refresh the list of movies with F5 after changing the filter settings (why doesn't that happen automatically?) and that most movies which i add with "new movie master" are added twice :-(

Reading in the WIKI explained that the latter happens when the spelling of title, original title and the spelling on the internet (eg in IMDB) don't match 100% exactly. but I couldn't find info on what it means to click checkmarks once (grey) or twice (white) in a movie selection dialog.

example: adding any title with a "different" spelling results in two entries with the original title (selected from the list), one with the typed title (as I would expect) and an URL "www.imdb.com/..." and a second entry which uses the original title as title and an URL "imdb.com/..." (added 10 seconds after the first). I also noticed that the effect might be related with the checkmarks on the movie selection dialog since it seems to happen only when a checkmark was clicked twice (making it white and not only grey).

my guess: only one checkmark can be grey and that is the entry which gets the typed title while all other checkmarks can only be white and their entries get their title set from the original titles to avoid having several identical titles. this is probably the intended behavior ?
and now the error: when there is no grey checkmark because of selecting only one checkmark and clicking it twice, PVD first (erronously) treats the selected movie like a grey one (adding it with the typed title) and then does the normal work of adding it with the original title as title like it does for all white checkmarks.


Quote from: nostra on September 09, 2009, 07:20:28 pm
Restore the backup from 0.9.9.11 ...
If you do not have a valid backup: ...instructions...

thanks for these instructions.
I don't know yet whether i need them (please note that i had written "using (of course after a backup :-) the old database"), but they give a lot of insight anyway :-)

ps: after typing this lengthy text and doing experiments for the above theories, i saw the new posts when previewing my own post ... seems to be best for me to stay with version 11 for a few hours and export my database which was created with v11, and then reimport it with v14 !?
besides some own or modified fields (like title) which fields do i need to export (to CSV) to uniquely identify movies for recreating the database? In theory a single URL should do but i probably have to use some dummy title too ?

Pages: [1]