On 2005-09-15, Jorge Godoy <godoy at ieee.org> wrote: > I just wonder when it becomes bad having to declare everything. For example, > we have databases with 600 tables. [snip] > Having the introspection is great in this case (even though it is boring > having to declare all those classes and tell them to fetch their structure > from the database it is better than having to "recreate" all of them). Granted. Also, if the tables share structure, another option would be to simplify their description with inheritance. > With regards to failures, this is one of the reasons for unit tests :-) They > can help finding out where is the problem and they should never fail > silently. You are right. I am consoled. js -- Jacob Smullyan
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4