What is the limit for the size of the integers on db ?

[garambois]

What is the limit for the size of the integers for an aliquot sequence on factordb.com ?

I tried to put on db my new aliquot sequence with record size primes (an aliquot sequence with pseudoprimes with more than 10000 digits), but impossible !
So, I put my result on my website :
http://www.aliquotes.com/back_3.txt

Does anybody know if it is possible to put this result on db ?

for an explanation on the principle of calculating the results, you can see the post N°7 of this page :
http://www.mersenneforum.org/showthread.php?t=18641

To see more results and new records of this kind :
http://www.aliquotes.com/remonter_suite_envers.html

To see an english summary of my website, with links to my databases and my open problems page :
http://www.aliquotes.com/resumesiteen.pdf

Thanks !

Jean-Luc

[Dubslow]

Could it be an issue with the GET request being too long?

https://www.w3.org/2001/tag/doc/get7#myths

Myth: URIs cannot be longer than 256 characters
This was a limitation in some server implementations, and while servers continue to have limitations to prevent denial-of-service attacks, they are generally at least 4000 characters, and they evolve as the legitimate uses of application developers evolve.

The other sequence you posted was less than 4000 digits, while the one you have here is a bit over 10K digits.

I'm quite certain the FDB can handle 10K digit numbers, the question is then how they are entered into the database if not via the "search" form on the homepage.

[garambois]

Thanks Dubslow.

Not more than 4000 digits !
OK, in the futur, I will put my results with more than 4000 digits on my website.

Jean-Luc

[Dubslow]

Originally Posted by garambois

Thanks Dubslow.

Not more than 4000 digits !
OK, in the futur, I will put my results with more than 4000 digits on my website.

Jean-Luc

I was only speculating. I have no idea if 4000 digits is an actual limitation of any sort or not. Best wait for others' input.

[science_man_88]

Originally Posted by Dubslow

I was only speculating. I have no idea if 4000 digits is an actual limitation of any sort or not. Best wait for others' input.

this one seem to come up for me roughly as the maximum digits for this factordb.com link 8160 digits but that changes slightly with the form of the sequences search. brb, with the minimum change you have to do to a index url to get a sequence url it takes about 1 digit away from the maximum by the looks of it. and that basically assumes no add ons like last entry index range etc. that would decrease it even more.

[garambois]

OK Dubslow,thanks.

Science_man_88, I put your big integer (3154852774...99<8160>) here :
http://factordb.com/sequences.php
And it doesn't work !
I don't know why ?
Can you put this integer in the same place with success ?

Jean-Luc

[science_man_88]

Originally Posted by garambois

OK Dubslow,thanks.

Science_man_88, I put your big integer (3154852774...99<8160>) here :
http://factordb.com/sequences.php
And it doesn't work !
I don't know why ?
Can you put this integer in the same place with success ?

Jean-Luc

I thought I could at one point but it doesn't seem to work anymore it's somewhat weird. but I most tried to play around to figure it out because that should give you a sense of what can work in each type of URL and such I'll see what I can do to refigure things out. edit: also did you take away the se= and such parts that may come up if not then that may cause it. it may be that I posted the index URL in my link the sequence limit would change it as well because sequences and aq have different amounts of letters to the total in index and query combined 11 in the first pair 10 in the second pair so the limit on digits drops by one just searching without any specifics. let alone with say the report url would change the limit slightly again depending on minimum formats. example for sequences would allow one less digit in the actually number part so:
this one should still work for you to try in the sequence form.

[Dubslow]

Hmm, starting with sm_88's link then clicking "Search" in the upper left gives a 400 Bad Request instead of a 414:

Bad Request

Your browser sent a request that this server could not understand.
Size of a request header field exceeds server limit.
Referer: http://factordb.com/sequences.php?...

Did Syd change the backend HTTP server when the FDB was down for maintenance yesterday? That's one possible explanation...

[bgbeuning]

Things like Oracle and SQL Server limit a row (and a column in a row) to something like 8100 bytes.
Unless the app is using a BLOB column and then the DB limit is over 2^32 bytes.

[science_man_88]

Originally Posted by garambois

So, I put my result on my website :
http://www.aliquotes.com/back_3.txt

I just randomly went through it and got that index 421 is the first smaller than the limit of the sequence lookup.

[garambois]

Originally Posted by science_man_88

I just randomly went through it and got that index 421 is the first smaller than the limit of the sequence lookup.

This was a good idea !
For me, the limit is at index 430.

This corroborates what bgbeuning said.

Jean-Luc