Re: Database access sucks!

From: Relaxin (me_at_yourhouse.com)
Date: 03/14/05 

Date: Sun, 13 Mar 2005 19:35:32 -0800

"Sean Hederman" <usemy@blogentry.com> wrote in message
news:d11tck$sfl$1@ctb-nnrp2.saix.net...
> "Relaxin" <me@yourhouse.com> wrote in message
> news:%23KJHGq%23JFHA.2784@TK2MSFTNGP09.phx.gbl...
>>
>> The Job that "I" have found that C# don't fit is when you need to load a
>> lot of data and 80% of it is varies pictures.
>
>
> Have a look at
> http://www.windowsforms.net/Applications/application.aspx?PageID=50&tabindex=8
>
> It's a .NET app that serves photos up to Windows Forms, Web Forms and CE
> clients.
>
>> I wish C#'s dataset had the ability to keep data at the server side
>> instead of loading it all to the client.
>
> Since a Dataset is a client-side disconnected data source this would
> completely be against it's design. If you want to iterate through back-end
> data with more fine-grained control, use the IDataReader implementations.
>

But, ADO supported server-side connections and I need it databound to a
grid.
So, the DataReader won't help.

>> Plus with .NET non-determisitic garbage collector, the client would
>> running out of memory or the system would become very sluggish.
>
> Actually, it doesn't matter what system you were running, pulling back a
> databases worth of images into memory will result in the same symptoms.
>
Not if most of it is keep on the server instead of the client.

>> Also, the inability to seperate your business logic from your interface
>
> I'm not sure what you're trying to get at here. If you're trying to say
> that .NET doesn't support n-tier architectures, you're very, very wrong.
> If you're trying to talk about the control of the actual UI being
> separated from the forms code itself, have a look at the Command pattern
> and
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag/html/uipab.asp
>
I'm not talking about n-tier, I mean not having to place you business logic
directly underneath your UI controls.
Borland handles this by means of a datamodule...which is where you place
your business logic and totally seperated from your interface.

>> The inability to change the key in the Keypress event.
>
> Events are not meant to be two-way data transfer mechanisms. About the
> only time events allow parameters to be passed back is when the event
> arguments support a Handled property. If you want to manipulate the text
> based on what key was pressed you can just do that. Another option would
> be to use the SendKeys class after setting e.Handled = true.
>

Borland allowed it, so you can't say it's not meant to be. It's just a poor
implementation on MS part.

>> The disassociation of your dataset from what the user is doing to it
>> through the components (mainly the grid).
>
> Dataset.Clone()
>
???... This just make a skeleton of your dataset without the data, now you
are also disassociated from your data.

>> And a semi-clunky IDE, although, there some things in the IDE that are
>> better than Borland's.
>
> Matter of taste I suppose. I personally find Borlands IDE horribly clunky.
>
>> Also, in C# (.NET 2.0), why do you need to select the class name
>> refactoring meun option. The IDE already knows the name of the class,
>> how about just automatically "refactoring" when I change the name
>
> Dunno about you, but I don't like the IDE doing stuff without my
> knowledge. What if I want to change the class name without anything else
> changing?
>
We are talking about changing the class name...you have to change it
everywhere if you want it to compile.
Are you just making up stuff to try to support MS decisions?

>> ...oh, and how about changing the name of the events (automatically)
>> also.
>
> Doesn't really apply to me, since I don't use the default event names
> anyway.
>
>> The product is just to immature.
>
> Not for me, not for my team, not for my company. We find it an absolute
> dream.
>
>> I just felt I would spend more time fighting and working around issues,
>> rather than writing code.
>
> Exactly why I like .NET ;D
>
> Isn't taste a strange thing?
>
Again, I think you are just making up arguments to support your decision.

I want .NET to succeed, I don't want to go back to Borland (for business
reasons), but I feel that currently I have no choice.

Relevant Pages

  • Re: i did it too... :-)
    ... > that allow OpenTools developers to access the IDE core and make add ins. ... Borland can be surely better than me at qualifying them in detail. ... Anyway I was speaking of services, not support in the stricter ... client is one thing and Quality Central ...
    (borland.public.delphi.non-technical)
  • Re: Win32, Linux, .NET >> Where is this mess going to?
    ... I already work with both Delphi and VS/C# - which I use depends on my ... Borland have always "lost" in the sense that more people used VS than ... forgot), D8 and now D2005 are a progression, changing from the old IDE ... Borland have no choice but to support .NET if they want to continue ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: D2007 for Win32, one short opinion
    ... I would have *loved* they announce 64 bits and unicode in VCL to be released *before* the support of .NET 3.0. ... I am probably an extremist, I clearly want Borland to cease .NET in Delphi, because I am disappointed by the trouble it has caused. ... the rest is just bugfixes (working help, no more IDE crashes, a decent debugger that handle multithread without freezing windows, a few compiler bugfixes) and the only improvements in speed and RTL seems to comes from FastCode or Pierre Le Riche's FastMM, some pple involved in the open source community and not hired by Borland. ...
    (borland.public.delphi.non-technical)
  • Re: Why arent you upgrading?
    ... I think most people are long past the point where they think that Borland ... massive support load for a fairly small group of people and not much room ... IDE or ancillary tools. ... programmers, has to pick the things it wants to focus on. ...
    (borland.public.delphi.non-technical)
  • Re: Borland Layoffs?
    ... The Borland IDE is definitely already pluggable. ... API in C#Builder 1 and Delphi 8 has limited support for adding new IDE ... support most everything the personalities would need before they could ...
    (borland.public.delphi.non-technical)
Loading