Re: Querying a DataSet/DataTable in .NET
- From: Ty Salistean <TySalistean@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 30 Dec 2005 08:41:05 -0800
Ok.
So I get all the basic tools to do remoting (protocols, etc..), but M$ built
that for me. I have all the tools to build a really cool DataGrid, but M$
gave me that too - and they keep trying to make it better.
So, I could write a SQL engine or....Maybe I dont get it. Thanks for the
post.
Anyone else with any thoughts?
"Marina" wrote:
> I don't think it's the same thing.
>
> The goal of .NET is to provide tools so that you could write the program you
> really need to, even if it means more work. So you have basic tools that you
> can use and put together for more advanced tasks. There are a lot of basic
> tools, and most of us only use a small subset of them.
>
> But that means there are not too many more advanced tools, which is what you
> are looking for.
>
> I just don't think you can compare a data-adapter, which is a pretty basic
> data manipulation mechanism, to writing an in-memory database engine.
>
> "Ty Salistean" <TySalistean@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:30C24DB9-CBEB-4DF1-8741-74A123B7B7CF@xxxxxxxxxxxxxxxx
> >I understand your point.
> >
> > But every .NET developer has access to a DataAdapter but may never use it.
> > This can be the same type of thing - it is available if you need it. This
> > is
> > just a suggestion as to how M$ can make their data handling better for
> > people
> > that handle these types of apps.
> >
> > Thanks for the post...
> >
> > "Marina" wrote:
> >
> >> When a technology is developed for writing very specific types of
> >> applications, then this can be done.
> >>
> >> ..NET can be used to program anything - video games, database access
> >> programs, etc. So it really becomes harder to provide features to
> >> accomodate
> >> everyone who may be writing anything. You may need this feature, someone
> >> else may really need something else, etc.
> >>
> >> "Ty Salistean" <TySalistean@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> news:576D5923-7967-4B40-9BC6-F7595E28056E@xxxxxxxxxxxxxxxx
> >> >I think it would be nice if we could have a SQL engine available on the
> >> > client side. I primarily do Windows Forms programming and it seems
> >> > that I
> >> > have to make alot of calls accross the wire to manipulate data for
> >> > display
> >> > purposes.
> >> >
> >> > I am a FoxPro guy but I have been in .NET for 1 year now. We have an
> >> > application in FoxPro hitting SQL Server and I think that system is
> >> > architected well. If I have a screen that requires the data to be
> >> > displayed
> >> > in a certain way that is completly different than how the data is
> >> > stored,
> >> > I
> >> > think that information should be generated client side - since it is a
> >> > for
> >> > display only (I could put it in business objects so I can reuse the
> >> > same
> >> > display in a different client). Either way - it is a display item.
> >> >
> >> > I need to do this in a SQL SP for .NET. I feel by placing this logic
> >> > in a
> >> > SQL SP, I am moving that logic to a 'procedural' based smart database.
> >> > I
> >> > have a problem with that. This just does not seem productive to me.
> >> > If I
> >> > switch my database, alot of my business logic will need to be
> >> > rewritten...
> >> >
> >> > How do we get M$ ear to ask for this? I think FoxPro got it right on
> >> > this
> >> > topic...hopefully .NET will follow.
> >>
> >>
> >>
>
>
>
.
- References:
- Re: Querying a DataSet/DataTable in .NET
- From: Marina
- Re: Querying a DataSet/DataTable in .NET
- From: Marina
- Re: Querying a DataSet/DataTable in .NET
- Prev by Date: Re: Querying a DataSet/DataTable in .NET
- Next by Date: Re: Querying a DataSet/DataTable in .NET
- Previous by thread: Re: Querying a DataSet/DataTable in .NET
- Next by thread: Re: Querying a DataSet/DataTable in .NET
- Index(es):
Relevant Pages
|