#1 Show Public/Private fields instead of public properties

[Anonymous]

Property accessors of classes are sometimes not
usable or accurate representations of what is in the data
if any formatting/etc. has to go on between the field and
the property accessor. It's much better to show only the
values of public and private fields so as to get an
accurate show of what is *really* stored in the database
instead of the processed output.

Submitted by:
efalsken@massie-labs.com

[Nobody/Anonymous]

Logged In: NO

Personally I feel this is a matter of opinion and I believe that both methods are useful. I definitely think viewing by field should be possible, but I don't personally believe that it should be locked in, one way or another; perhaps enabling/disabling public, protected, and private field/property access is in order.

One other reason why this may be useful is in finding logic errors in stored objects; occasionally when entities get complex enough there may be the scenario where a property is not returning the expected value in relation to the field/fields it is associated with. Under this circumstance it would be very handy to have both enabled to be able to cross-reference.