Problems scanning certain movies

[leogets]

I'm running Windows 7 Pro x64 and using PVD v1.0.2.7

I'm having a problem with a movie, the movie is  called 'Inherent Vice (2014)' this movie is also a t.v show series. I kept getting an arithmetic error that I could not find a way to get rid of and had to start the scanning of all my movies all over again.
The url to the movie is: http://www.IMDb.com/title/tt1791528
But even entering it manually and try to scan movies to update older info like the IMDB votes, I still was getting the arithmetic error and I don't know why.  I keep getting the viddb error:
arithmetic exception, numeric overflow, or string truncation string right truncation
At procedure 'GET_TAGS' line: 1, col:321
Arithmetic overflow or division by zero has occurred.
Error Code: 1.

[mgpw4me]

The clues:
(1) Error occurs in procedure GET_TAGS
(2) IMDB indicates 548 plot keywords
(3) There is an "overflow"...the program can handle X number of items, and you tried to add X + 1.

548 is a lot of tags.  GET_TAGS (or some subroutine it uses) probably can't handle 548 items.

Once a program has an overflow value, that value is (probably) NULL and using NULL as an index in the database would certainly corrupt it.

Try:

Personal Video Database -> Preferences -> Plugins -> IMDB Movie Information -> Configuration -->> UNCHECK the "DOWNLOAD ALL TAGS" checkbox.

With a NEW (empty) database, try to download the movie again.  You should get the movie info with 5 tags. 

If so (and you dare..backups are always good  ), you can rescan the movie in your "production" database, then change the configuration for the IMDB Plugin so it only adds tags if there are none and re-enable the "download all tags" checkbox:

no checkmark = never update
checkmark     = always update
blue box        = only update if empty.

NOTE: You could probably do a database repair rather than rebuild the database from scratch. 
http://www.videodb.info/forum_en/index.php/topic,3935.0.html

NOTE 2:  If you scan IMDB with the "always update" option for tags, it "should" delete all the "bad" tag entries and replace them with the 5 good ones.  Not tested, but there's nothing to loose...and your database would no longer be corrupt if it works.

NOTE 3: The PVD database can handle 2 billion tags of 127 characters each.  Firebird can handle SQL statements up to 64k (transactions...multiple SQL statements, treated as a group must fit into the same space...548 inserts = 1 transaction).  Given that the 548 tags are about 10k in size, and the SQL statements that would be required would still be under 64k, I think the problem is with the space PVD allocates for an SQL statement / transaction.  The point of this note is that the number of tags isn't the problem...it's the length of all the SQL statements that are required to do the necessary processing.  Firebird can handle it, but PVD can't.