You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The way SQL map displays results after a query is finished running is nice. Basically they format the table like
*Here is my Query *
Results
*Results
*Results
*78 rows and took 389 seconds
They then clip any query that is more than I think 80 Rows (since viewing that in a terminal window can be a little much) and default to spit the output in a file if the query returns back a ton of data (think dumping 80,000 hashes for example).
The text was updated successfully, but these errors were encountered:
The way SQL map displays results after a query is finished running is nice. Basically they format the table like
*Here is my Query *
Results
*Results
*Results
*78 rows and took 389 seconds
They then clip any query that is more than I think 80 Rows (since viewing that in a terminal window can be a little much) and default to spit the output in a file if the query returns back a ton of data (think dumping 80,000 hashes for example).
The text was updated successfully, but these errors were encountered: