Reverse guessing of database column names through interface field names

For example, we can see the following json field through the interface capture. userName
We have reason to believe that the column name corresponding to this field in the database is user_name
searching the table and database that uses this column_name through the information_schema reverse to locate the database.
select * from information_schema.columns where column_name = 'user_name'

Of course, the main factor that does not work in this way is whether the developer has performed additional processing.

That is to say, camel case nomenclature and underscore nomenclature, these two naming methods correspond to the same data.

Next, let's talk about the information_schema library.

Guess you like

Origin blog.csdn.net/lineuman/article/details/115356959