Page 1 of 1
Fixed [BUG 3.20] database problem
Posted: Mon Mar 09, 2009 5:52 pm
by duduche
Hi,
I have installed RC3.20 (before i was on 2.71) but now datafile are in xml format, great it not compatible with 2.71, so i pass to 3.20. AND nice RC3.20 doesn't load datafile!!!
And if i do manualy open RC ask me a .rdt ???? What ???
The file are .zip with .txt or .dat in and if load one of this i have the message :
file C:\DOCUMENTS AND SETTINGS\C-DRIK.SATELLITE-1\APPLICATION DATA\ROMCENTER\DATAS\CPS-2 20081018.DAT is not a valid database
WHATS THE PROBLEM.
Thanks.
Bye.
Re: RC3.20 database problem
Posted: Mon Mar 09, 2009 8:28 pm
by RomCenter
Hi
You must do something wrong. Read the
quickstart guide and come back if you still have problems.
Re: RC3.20 database problem
Posted: Mon Mar 09, 2009 11:24 pm
by duduche
hi
yes i found i must create .rdd with .dat (why doesn't give them directly? too big?).
but i have problem with :
Daphne 0.99.7.rdt :
Plug in not found
RAINE 0.51.0.rdt :
Erreur: multiple rows in singleton select
At procedure 'P_UPDATEROMID'
At procedure 'P_LOADFILES'
Thanks.
Bye.
Re: RC3.20 database problem
Posted: Tue Mar 10, 2009 8:44 pm
by RomCenter
I will try to reproduce both problems.
Thank you for reporting.
Re: Fixed [BUG 3.20] database problem
Posted: Tue Jun 23, 2009 3:07 am
by odelta
Hello, I just wanted to confirm an error similar to the one that duduche reported. After loading a rom path I get the following error:
Error: multiple rows in singleton select
At procedure 'P_UPDATEROMID'
At procedure 'P_LOADFILES'
multiple rows in singleton select
Error Code: 332
Ready
I'm using RC 3.31 and I tested this on 2 different systems: Windows XP SP3 and Windows Server 2008 SP1. I've attached my log file. Hopefully with enough information we can help solve the issue. Let me know if you need any other info. Thanks.
Re: Fixed [BUG 3.20] database problem
Posted: Sat Jun 27, 2009 7:08 am
by RomCenter
Thank you for the log.
It's quite hard to tell what's wrong, there are a lot of files which can cause the problem.
Before going further, please wait for the version 3.40 to see if that problem is fixed. I almost finished the tests.