let the database digest all the number its already working on.
to be honest, I hope Syd open the possibility to be a 'worker' to help it

[quote=Andi47;227005]Have they been added in the last few days? In his posting above, Syd said that he used a few-day-old backup of the old DB to build up the new one.[/quote]


No the most of the known factors are old.

Getting an error when trying to do anything at the DB:
[QUOTE]Warning: mysql_connect() [function.mysql-connect]: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) in /apache/htdocs/database.php on line 6
Could not connect to database[/QUOTE]

now : Updating tables .. this will take about 20 min

it seems that the report factor does not work... tried to insert in background or not.

The Scan button is currently not working: when you click on it, no matter which level it does, it returns without a factor almost immediately.

I reported these factors of 10^999+1:
[code]902659997773
58390995742813
7116181512528105949933
62562101977662753776437
21606064498691505246200058094681
48911689110891303706174193415115219
2490872691908137575166466088291355643827701079891978578274835994080775464595974553558911862020407649324804027436087292675616017146240063168618749945139990951997
[/code]

It worked properly.
Scan button also works. :smile:

Is there some limitation (length of lines, etc.) or bug in the parser at the "report factors" subpage (i.e. [url]http://factordb.com/new/report.php[/url] )?

I tried to report a few lines of aliquot sequence 10212 (from a .elf file), but even several hours later the factors did not make it into the DB. (note: this sequence is currently at 142 digits.)

I pasted this into the "report factors" subpage:

[code] 2315 . 4214750023953689805501329052475121257605021418538549143227647496884708377113732488093448276170817806429801068326477094140211443974604367868118 = 2 * 3 * 17 * 61 * 1489 * 131129137 * 244082138697195595406420828875227643956166661 * 14213856096249480043842463784632572582202081014212913643784779131081193588038192953
2316 . 4863012757534371638148798168433324802232037631661223607783619148325476175392099134319013535416600950635932575283476582790085817006229343797802 = 2 * 3 * 61 * 461 * 140275541914953600037298293 * 205466698660761647634622651298455556094759477756477889826648064568878445819815438880250933651563442704513579139
2317 . 5043899331425092193374559872150022231614341266127078791636395497540657976375903031110966838081523321421429337468127066910749396202152610734678 = 2 * 3 * 13^2 * 41 * 94397 * 2982468168293597853415117953200775265423 * 430933829648348607654712679226371403606906684599113194416474889190132530046630336251197311187
2318 . 6146119703386150825448489914838895231185287181957358109672692741978648326567477930970238163500618833568311753086295878281532411226419257264554 = 2 * 3 * 5903587 * 908411951 * 191007736099941266526727091455140723506665525577032142424350082378718626234250806277657549681243320053126418597770147250826307
[/code]

Edit: Maybe the bug is about the leading "blank" character at the beginning of each line?

Edit2: I just tried after deleting the leading "blanks" - the factors have not (yet?) arrived in the DB.

P.S.: The box "insert in background" was [I]not[/I] checked.

P.P.S.: This time I did NOT report the factors one by one [URL="http://factordb.com/new/index.php?id=1100000000211955635"]here[/URL] (I know this to work) to leave this as a test case.

[QUOTE=Andi47;227260]Is there some limitation (length of lines, etc.) or bug in the parser at the "report factors" subpage (i.e. [url]http://factordb.com/new/report.php[/url] )?

I tried to report a few lines of aliquot sequence 10212 (from a .elf file), but even several hours later the factors did not make it into the DB. (note: this sequence is currently at 142 digits.)

I pasted this into the "report factors" subpage:

[code] 2315 . 4214750023953689805501329052475121257605021418538549143227647496884708377113732488093448276170817806429801068326477094140211443974604367868118 = 2 * 3 * 17 * 61 * 1489 * 131129137 * 244082138697195595406420828875227643956166661 * 14213856096249480043842463784632572582202081014212913643784779131081193588038192953
2316 . 4863012757534371638148798168433324802232037631661223607783619148325476175392099134319013535416600950635932575283476582790085817006229343797802 = 2 * 3 * 61 * 461 * 140275541914953600037298293 * 205466698660761647634622651298455556094759477756477889826648064568878445819815438880250933651563442704513579139
2317 . 5043899331425092193374559872150022231614341266127078791636395497540657976375903031110966838081523321421429337468127066910749396202152610734678 = 2 * 3 * 13^2 * 41 * 94397 * 2982468168293597853415117953200775265423 * 430933829648348607654712679226371403606906684599113194416474889190132530046630336251197311187
2318 . 6146119703386150825448489914838895231185287181957358109672692741978648326567477930970238163500618833568311753086295878281532411226419257264554 = 2 * 3 * 5903587 * 908411951 * 191007736099941266526727091455140723506665525577032142424350082378718626234250806277657549681243320053126418597770147250826307
[/code]

Edit: Maybe the bug is about the leading "blank" character at the beginning of each line?

Edit2: I just tried after deleting the leading "blanks" - the factors have not (yet?) arrived in the DB.

P.S.: The box "insert in background" was [I]not[/I] checked.

P.P.S.: This time I did NOT report the factors one by one [URL="http://factordb.com/new/index.php?id=1100000000211955635"]here[/URL] (I know this to work) to leave this as a test case.[/QUOTE]

Seems it's not just me: Sab reports the same bug (for an other sequence) [URL="http://www.mersenneforum.org/showpost.php?p=227348&postcount=99"]here[/URL], so it seems that parsing .elf files (or redirecting the factors to the new DB) is broken.

Edit: My factors from aliquot sequence 10212 are still not in the DB - almost 24 hours seem too long to be explained by a long input queue.

Time for a small update:

I found and fixed some of the bugs you mentioned, namely:

- The scan button didnt work for numbers above ~2000 digits, it just returned without doing anything cause it had no ECM parameters. Now it has them for up to 9500 digits. If it has none, the button dosnt even show up.

-The report factors form was buggy when using some formats, it didnt split up the factors correctly. Now it does, at least for the .elf-files I tested.

-A lot of factors from the old db are still missing - now I know why. I'll try to convert them over later.

Some changes:

- The scan button now has an "alt" tag showing what the scan will exactly do. It should show up after placing the cursor on the button for a second.

-The first scan level, 100ms, was removed. Now it does it together with the next one, 300ms, at once.

-The "more Information" search now also shows if the number has predecessors in any sequence, if stored in the database. Maybe this is useful to some of you.

More in a few days!

Reporting .elf files works for me now. :tu: Thanks for that and the other fixes/changes. One thing, though:
[QUOTE=Syd;227835]- The scan button now has an "alt" tag showing what the scan will exactly do. It should show up after placing the cursor on the button for a second.[/QUOTE]

Please put this in a "title" tag instead of (or in addition to) an "alt" tag so that browsers besides IE (like Firefox and Chrome, at least) will have the desired behavior.