Ed Leafe wrote:
> On Mar 30, 2007, at 9:53 PM, Larry Bradley wrote:
> 
>> Remote views are a lot simpler than using passthrough. You update a  
>> field
>> (or fields), do a tableupdate(), and VFP takes care of all the  
>> messy stuff
>> - conflict resolution, determining which fields have to be written  
>> back,
>> buffering, transactions, etc ad nauseam.
>>
>> With passthough, you have to handle all these details yourself.
> 
>       Have you ever seen Paul's makeUpdatable.prg? It basically does all  
> the things that views do, but allow you the flexibility of using SPT  
> for your code.
> 
>       I've written several data access classes in VFP that integrate  
> makeUpdatable with SPT, giving you the best of both worlds. That's  
> what I've tried to do with Dabo's database layer.
> 

I disagree with the "basically does all the things that views do" if you take 
into consideration the maintainability factor.  to me a view is just metadata, 
no code.  SPT is code.  code is more flexible than metadata, but also more 
fragile.  thinking of the unit tests, I can't really see writing a test that 
would test metadata.  I can see writing a test that would test the code that 
uses metadata, but that gets done once and the code is fairly stable/solid.
.
for the most part I don't need the flexibility, so to me it makes sense to rely 
on views and the various "view editor" tools, like Rick's ViewEditor and VFE's 
DBCX explorer.  these are basicaly UI's around the wad of settings that can be 
tied to a view by ViewName or View.Field name.  to me, that is the reason for a 
view - totaly design time.  assuming a bug free stable finished program (which 
I 
have never seen, but anyway) I don't think the user would ever know or care if 
it used views or SPT.  so the view concept is totally a developer thing.

VFE has a similar but completely different counter part to makeUpdatable.prg - 
it starts with an updateable view, sucks the SQL out of it, augments it (adds 
WHERE expressions), executes it with SPT and APPENDS the results into the empty 
view cursor.

What I would like to see in dabo is some sort of meta data based thing.  but I 
am still very foggy as to exactly what it is and how it would be implemented.

VFP's cursor adapter seemed interesting, but I never got around to using it. it 
could be subclassed, which sounds useful, but I have yet to hear of that 
actually being done.

Carl K

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/dabo-users|[EMAIL PROTECTED]

Reply via email to