[DUG] Connectionless recordsets

[Jeremy Coulter]

Yeah Jolyon, thats right. Although I am going t be TRYING not to expose the
GUI to the DB layer, and I think I can do that. However, at this stage I
dont think I will be dropping ADO for awhile. And David, I will need to
update the source data, but that will be via functions calling stored procs
and then just reloading the data as needed. I still have a few things to
work thru, but glad to know I am on the right track :-)  didnt want to get
to the implementation stage and then go...."opps...!" :-)

Jeremy


On Mon, Nov 4, 2013 at 8:18 AM, Jolyon Smith <jsmith at deltics.co.nz> wrote:

>
> Disconnected record sets are nothing new and there's no reason to not use
> them other than the usual one(s) of "as long as it is appropriate in any
> particular case and there simply isn't enough information here to say
> whether it may be inappropriate in this one.  :)
>
> One concern that may or may not be pertinent is that by directly exposing
> a component of your database layer it is effectively poking through the
> business layer and into the GUI layer.  Should you ever find yourself
> needing to abandon ADO in the future, your TADODataset cannot be replaced
> without impacting directly on the code in the business layer that works
> with it or the code in the GUI layer.
>
>   Jeremy Coulter <jscoulter at gmail.com>
>  Mon, 4 Nov 2013 07:57
>
> Hi all.
>
> I am in the process of redeveloping an existing application that has
> reached the end of its ability to add stuff nicely without breaking other
> bits of the code. Admittedly best practice was not always followed J but
> its time to start version 2 of the app.
>
> As part of this I am splitting stuff up into database, business and GUI
> layers – on paper at the moment, and a thought occurred to me. In .Net
> which I sometime work in, you uses datasets which are basically
> connectionless, and I wondered if anyone can think why I would not take a
> similar approach. I am using ADO, and at the moment I have a test procedure
> that calls a stored proc, then passes back a TADODataset which is not
> connected to any database, connectionless, then this procedure “does
> something” with the recordset, just looping it and printing stuff to a
> listbox at the moment.
>
> When its done, it frees the object etc.
>
> Can anyone see anything wrong with this approach? Or things I should be
> aware of etc?
>
>
>
> Thanks, Jeremy
>
>
> _______________________________________________
>
> NZ Borland Developers Group - Delphi mailing list
> Post: delphi at listserver.123.net.nz
> Admin: http://delphi.org.nz/mailman/listinfo/delphi
> Unsubscribe: send an email to delphi-request at listserver.123.net.nz with
> Subject: unsubscribe
>
>
> _______________________________________________
> NZ Borland Developers Group - Delphi mailing list
> Post: delphi at listserver.123.net.nz
> Admin: http://delphi.org.nz/mailman/listinfo/delphi
> Unsubscribe: send an email to delphi-request at listserver.123.net.nz with
> Subject: unsubscribe
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://listserver.123.net.nz/pipermail/delphi/attachments/20131104/435fc27f/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 770 bytes
Desc: not available
Url : http://listserver.123.net.nz/pipermail/delphi/attachments/20131104/435fc27f/attachment-0001.jpe