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
This doesn't represent a problem (apparently), but it's a good practice and also a recommendation to improve performance, to list only the columns that are expected to be used. In this case, this columns are used by the classes mx.nic.rdap.sql.objects.*DbObj. So I recommend that instead of using the wildcard, the queries should return the columns expected by the java objects.
The text was updated successfully, but these errors were encountered:
Also, listing the column names in the queries could save some reading time to someone that wishes to modify the queries; yes: it's more text, but the query is more explicit.
Some of the queries use the asterisk wildcard to get all the columns from a table, just to say a few:
This doesn't represent a problem (apparently), but it's a good practice and also a recommendation to improve performance, to list only the columns that are expected to be used. In this case, this columns are used by the classes
mx.nic.rdap.sql.objects.*DbObj
. So I recommend that instead of using the wildcard, the queries should return the columns expected by the java objects.The text was updated successfully, but these errors were encountered: