Re: Data Access...
- From: "Ty Salistean" <tsaliste@xxxxxxxxx>
- Date: Wed, 8 Jun 2005 15:07:25 -0500
I will say that by using an ANSI standard for re-filtering data is still a
better option. Someone coming to .NET from and SQL compliant language would
be able to understand the syntax alot better. What other manipulation tool
would accomodate everyone?
> How is a SQL engine a compromise? It's a *lot* of work, and in many
> cases still wouldn't give as much ease and flexibility (and compile-
> time type safety) as a callback-based filter.
I am sure data technologies such as RDO, DAO, and ADO were not easy to
accomplish. Why did they suck? Data manipulation, navigation, etc...
> Well yes, but there are also plenty of apps which save data but don't
> need to use a database. Most word processors don't have databases in
> them, for example...
We can discuss this all day. Then do NOT include the System.Data.SQL.dll
(or whatever) with your app.
At least we can agree that if you are working with data, it would be nice to
have some other way to process that data easily. To be completely honest, I
do not care how they do it...simply realize the need is there...
"Jon Skeet [C# MVP]" <skeet@xxxxxxxxx> wrote in message
news:MPG.1d11572ad44b26e998c29a@xxxxxxxxxxxxxxxxxxxxxxx
> Ty Salistean <tsaliste@xxxxxxxxx> wrote:
> > > I don't see why. Not every application needs a database. I bet there
> > > are people out there who've programmed in SQL but have never written a
> > > C# app - but I don't see that as a problem either, do you?
> >
> > I agree with you. I should have made myself more clear. But, I did say
in
> > my original post
> >
> > > > The ability to requery data on the client is an essential tool for
every
> > > > developer, unless you never save your data.
>
> Well yes, but there are also plenty of apps which save data but don't
> need to use a database. Most word processors don't have databases in
> them, for example...
>
> > I said this - but I would still like some other tools for data
manipulation.
> > The type of manipulation you want to do may not be the same manipulation
> > that I want to do. The only way to do this is give us tools that do
what we
> > need to do. I would think a SQL Engine would be an excellent
comprimise.
> > This can be done through an inclusion.
>
> How is a SQL engine a compromise? It's a *lot* of work, and in many
> cases still wouldn't give as much ease and flexibility (and compile-
> time type safety) as a callback-based filter.
>
> > If you do not need it, then do not use it. There is a lot of
functionality
> > that i never use but I get it - I am sure the same is true for you...
>
> Yes, but the suggestion I made would give a lot of flexibility for a
> vast amount less cost in terms of both work and framework size.
>
> --
> Jon Skeet - <skeet@xxxxxxxxx>
> http://www.pobox.com/~skeet
> If replying to the group, please do not mail me too
.
- Follow-Ups:
- Re: Data Access...
- From: Jon Skeet [C# MVP]
- Re: Data Access...
- References:
- Data Access...
- From: Ty Salistean
- Re: Data Access...
- From: Jon Skeet [C# MVP]
- Re: Data Access...
- From: Ty Salistean
- Re: Data Access...
- From: Jon Skeet [C# MVP]
- Data Access...
- Prev by Date: Re: Data Access...
- Next by Date: Cannot save file to network: UNC path should have the form \\server\share.
- Previous by thread: Re: Data Access...
- Next by thread: Re: Data Access...
- Index(es):
Relevant Pages
|