SQL_connection = db_conection;
SQL_db = the box;
SQL_rows = user_name, user_id;
SQL_ext = mysql;
SQL_command = select;
SQL_amount = *;
SQL_result ;
SQL_rows_join = user_apps;
if (SQL_query())
{
}
else if (ut_sql())
{
}
else if
help_info_sql(){
}
If the SQL query fails it runs the unit test, also adding a new step to unit tests (the help info), depending on the error's that the unit test detects we get help information. Lets say this example : that unit test detects a invalid row, it says one or more rows invalid, but that does not fix the error. so the help info will get information based on the error for us. Instead or prevent us from going to the db to check it. we get the rows that are there associated width the call. so that we can see directly in the code where is the error.
This is possible because we fragmented the code or command in to parts.
let see how it evolve... Think all code and our knowledge is evolving.
Thursday, February 29, 2024
Pseudo Object on SQL Built in a stack library
Subscribe to:
Posts (Atom)
hi
Rules
Rules, Steps & methods This is the current way to implement and be implemented but there could be more things to add : Root or loader (...
-
Personal tastes All come down to personal preferences, we can't control all things. This style works, it have it's positive and ne...
-
Add the Data verifier component to the DTR. When we add something we can also check for errors. Is still a bit messy but is a evolution from...
-
Sorry for the delay on news but think any one can understand the current world events. For a long time i was not able to work on the project...