> Unfortunately it doesn't work so well if you want to go
> to the next logical step and have all of your data
> selection via stored procs - it's not really possible to
> write good select stored procs which handle multiple
> possible filter parameters.
I have had no trouble in this area, but maybe I don't provide filtering of
result sets to the same extent that you do. Where I have provided this,
I've tended towards implementing many short specific stored procedures
rather than bigger, more generic ones.
How many possible filter parameters are you providing for a single view or
table?
Paul Ritchie
Radio Computing Services
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
- Re: [DUG]: embedded database. Xander van der Merwe
- Re: [DUG]: embedded database. Neven MacEwan
- RE: [DUG]: embedded database. Myles Penlington
- Re: [DUG]: embedded database. Neven MacEwan
- RE: [DUG]: embedded database. Myles Penlington
- RE: [DUG]: embedded database. Paul Ritchie
- Re: [DUG]: embedded database. David Brennan
- Re: [DUG]: embedded database. Neven MacEwan
- Re: [DUG]: embedded database. David Brennan
- Re: [DUG]: embedded database. Neven MacEwan
- Re: [DUG]: embedded database. Paul Ritchie
- Re: [DUG]: embedded database. David Brennan
- RE: [DUG]: embedded database. Paul Ritchie
- RE: [DUG]: embedded database. Paul Ritchie
- Re: [DUG]: embedded database. Neven MacEwan
- RE: [DUG]: embedded database. Paul Ritchie
- Re: [DUG]: embedded database. Neven MacEwan
- Re: [DUG]: embedded database. David Brennan
- Re: [DUG]: embedded database. Neven MacEwan
- Re: [DUG]: embedded database. Neven MacEwan
