This website requires JavaScript.
Explore
Help
Register
Sign In
Hiddenden
/
beef
Watch
2
Star
0
Fork
0
You've already forked beef
Code
Issues
Pull Requests
Actions
Packages
Projects
Releases
Wiki
Activity
Files
1486812e96a77cfcd9b2d3b25eeecd8b0b4e2214
beef
/
core
/
main
/
models
History
antisnatchor
6d19b04f60
Using _ instead of . for DB table names: this convention ([a-z0-9_]) follow best-practices, and in this way there is no need to use a backtick when writing sql queries in MySQL (or in the future PostreSQL)
...
git-svn-id:
https://beef.googlecode.com/svn/trunk@1033
b87d56ec-f9c0-11de-8c8a-61c5e9addfc9
2011-06-27 14:26:44 +00:00
..
command.rb
Files tidied and renamed variables.
2011-04-20 12:21:19 +00:00
commandmodule.rb
Using _ instead of . for DB table names: this convention ([a-z0-9_]) follow best-practices, and in this way there is no need to use a backtick when writing sql queries in MySQL (or in the future PostreSQL)
2011-06-27 14:26:44 +00:00
dynamiccommandinfo.rb
Using _ instead of . for DB table names: this convention ([a-z0-9_]) follow best-practices, and in this way there is no need to use a backtick when writing sql queries in MySQL (or in the future PostreSQL)
2011-06-27 14:26:44 +00:00
dynamicpayloadinfo.rb
Using _ instead of . for DB table names: this convention ([a-z0-9_]) follow best-practices, and in this way there is no need to use a backtick when writing sql queries in MySQL (or in the future PostreSQL)
2011-06-27 14:26:44 +00:00
dynamicpayloads.rb
Using _ instead of . for DB table names: this convention ([a-z0-9_]) follow best-practices, and in this way there is no need to use a backtick when writing sql queries in MySQL (or in the future PostreSQL)
2011-06-27 14:26:44 +00:00
hookedbrowser.rb
Using _ instead of . for DB table names: this convention ([a-z0-9_]) follow best-practices, and in this way there is no need to use a backtick when writing sql queries in MySQL (or in the future PostreSQL)
2011-06-27 14:26:44 +00:00
log.rb
Using _ instead of . for DB table names: this convention ([a-z0-9_]) follow best-practices, and in this way there is no need to use a backtick when writing sql queries in MySQL (or in the future PostreSQL)
2011-06-27 14:26:44 +00:00
optioncache.rb
Using _ instead of . for DB table names: this convention ([a-z0-9_]) follow best-practices, and in this way there is no need to use a backtick when writing sql queries in MySQL (or in the future PostreSQL)
2011-06-27 14:26:44 +00:00
result.rb
Using _ instead of . for DB table names: this convention ([a-z0-9_]) follow best-practices, and in this way there is no need to use a backtick when writing sql queries in MySQL (or in the future PostreSQL)
2011-06-27 14:26:44 +00:00
user.rb
Using _ instead of . for DB table names: this convention ([a-z0-9_]) follow best-practices, and in this way there is no need to use a backtick when writing sql queries in MySQL (or in the future PostreSQL)
2011-06-27 14:26:44 +00:00