On 2016-11-25 15:29, Lester Caine les...@lsces.co.uk [firebird-support]
wrote:
> On 25/11/16 13:56, Mark Rotteveel m...@lawinegevaar.nl
> [firebird-support] wrote:
>> On 2016-11-25 12:40, Lester Caine les...@lsces.co.uk
>> [firebird-support]
>> wrote:
>>> > Nothing to do with Firebird but can
On 25/11/16 14:11, fabia...@itbizolutions.com.au [firebird-support] wrote:
> Are you trying to store details of the American public debt? or the world's
> public debt? Just kiding Not
See other post ;)
It is vulnerability to overflow edge cases that are the potential
problem - especially in
On 25/11/16 13:56, Mark Rotteveel m...@lawinegevaar.nl
[firebird-support] wrote:
> On 2016-11-25 12:40, Lester Caine les...@lsces.co.uk [firebird-support]
> wrote:
>> > Nothing to do with Firebird but can anybody explain why the numbers in
>> > 'SELECT FIRST 102121121121212 SKIP 3574239239242420'
Are you trying to store details of the American public debt? or the world's
public debt? Just kiding Not
How about assigning another integer field to each record with a value
representing the "segment" for the value you are trying to store, and then
use an index on that value, I'll explain
On 2016-11-25 12:40, Lester Caine les...@lsces.co.uk [firebird-support]
wrote:
> Nothing to do with Firebird but can anybody explain why the numbers in
> 'SELECT FIRST 102121121121212 SKIP 3574239239242420' would be a problem
> in MySQL or is it some other vulnerability the original sQL injection
Nothing to do with Firebird but can anybody explain why the numbers in
'SELECT FIRST 102121121121212 SKIP 3574239239242420' would be a problem
in MySQL or is it some other vulnerability the original sQL injection
was trying to hit. I know I need to add limit checks in the code which
reprocessed
