| T O P I C R E V I E W |
| mbaram |
Posted - 19 Nov 2005 : 18:43:07
I wrote about this before, the view by ID numner is in order of 10..100...101...11 instead of 10...11...100...101 |
| 8 L A T E S T R E P L I E S (Newest First) |
| mbaram |
Posted - 27 May 2006 : 12:58:09
I just got 5.2.4 version - the problem is still there... Alessio, can you please fix it???
 |
| jamestan |
Posted - 15 Dec 2005 : 02:25:18
Even though it is in theory it could go up to 99999 movies, it is not a good database to store such a huge information. Providing an automatic upsize feature to database like MS SQL Server or Oracle would be very nice.
quote:
Originally posted by Ian
excellent work Rincewind. This problem gives me great irritation. I hope your suggestion works. As soon as I read it, I realize I use the same trick already in Excel and also on numbered folders. Very smart of you to suggest this solution
as for number of movies. I agree that XMM should be prepared for movie id's up to 99,999 to be safe. And if it does not make an programming difference that 999,999 will definately guarantee no one has any problem 
|
| Ian |
Posted - 14 Dec 2005 : 00:08:39
excellent work Rincewind. This problem gives me great irritation. I hope your suggestion works. As soon as I read it, I realize I use the same trick already in Excel and also on numbered folders. Very smart of you to suggest this solution
as for number of movies. I agree that XMM should be prepared for movie id's up to 99,999 to be safe. And if it does not make an programming difference that 999,999 will definately guarantee no one has any problem |
| Alessio Viti |
Posted - 12 Dec 2005 : 20:11:29
OK MTS |
| MTS |
Posted - 01 Dec 2005 : 19:45:09
If you do it like that, then i suggest to use more than 3 digits. I have more than 1000 movies in db, and maybe someone someday has more than 10.000  |
| Alessio Viti |
Posted - 22 Nov 2005 : 21:19:42
Hi Ricewind,
Yes, this can be a solution, I think I will do this instead of changing the DB structure.
Thank you!
Alessio |
| Rincewind |
Posted - 21 Nov 2005 : 20:30:53
none of my business but . . .
I presume the problem arises because the field containing the DVD ID is defined as character.
One simple solution (without changing anything) is to ensure all DVD ID values are of the same length. (I've been caught before so I started mine at 100 not expecting to go past 999 and dont have a problem).
I suspect if you put leading spaces or leading zeros (2 in front of a single digit e.g. 1; 1 in front of a double digit e.g. 11) the problem will go away. |
| Alessio Viti |
Posted - 19 Nov 2005 : 20:44:25
Sorry, it's an old problem, related to DB structure, I am trying to find a solutions without change the DB structure.
Thank you!
Alessio |
