Good,
I was looking forward to the release of subsonic 3.0 for use as my low-level data layer, and now its release. I am currently using ActiveRecord templates (tried both the repository and advanced templates), and I have one HUGE request and a few questions:
Request: in addition to fixing bugs, please take the time to provide documentation. I do not mean 5 examples, I mean the full API documentation. That's why:
I test subsonic by writing ASP.NET MembershipProvider and RoleProvider classes, and simple questions constantly slow me down with subsonic:
Q. Assuming I have a class "User" and I am updating / saving / deleting a record with
user.Save();
I need information on how to succeed / fail? Am I looking for an exception on error, or can I get the number of “affected” entries (old school?)
Q. If I get an exception, what exception (s) can I expect?
I will have more problems, but I really believe that a good functional API documentation will solve this problem.
If the answer is “read the source code,” then I’m sure that you are going to pursue several subsonic developers. I really want to use the library, but the fact is that it "uses" the library, and not vice versa.
-Jeff
source
share