Application development pointers

[sqlguru]

Did I or didn't I read the documentation?make your mind up. Iam crazy to
know where I should have put this translation? Some entity that we dare not
call a provider, or ORM or DAL. Come on hotshot explain to us mortals rather
than telling us to read books because that makes me think you are just a
troll.

Troll, you would put this conversion method preferably in your custom
common framework. You do have a custom framework right? There is no
need for your "provider" to be in the custom framework cause the
ADO.NET "common" framework already has a perfect implementation for
all databases. You're supposed to read the DB vendor's .NET provider
for the inference of DBType.

I create my own DAL/ORM that converts IDataReaders to model objects yes. I
said I dont use the entity framework/linq/datasets.

First you said you used a "provider". Now you use an ORM and now
you're getting your DAL and ORM mixed up.

 

[Paul]

Troll, you would put this conversion method preferably in your custom
common framework. You do have a custom framework right? There is no
need for your "provider" to be in the custom framework cause the
ADO.NET "common" framework already has a perfect implementation for
all databases. You're supposed to read the DB vendor's .NET provider
for the inference of DBType.

No it does not or I would have used it.

Map a Clob to dbtype then map back again to a sqldbtype. Wow you can't
without abstracting it off and thats just one example for ODP.NET and
SQLClient, think of all those other providers. Before you tell me to read
that document trust me I read it years ago. I came up with a solution then
that works and still does you don't like it, then im still waiting for your
expert advice on how it should really be done.

First you said you used a "provider". Now you use an ORM and now
you're getting your DAL and ORM mixed up.

No Im not Do you know the difference between a DAL and an ORM or should I
say similarities.

I have an abstraction that allows me to create a DAL/ORM with no reference
to Specific ADO.NET providers. It also allows me to still do database
specific tasks and gain performance benefits associated with specific vendor
providers.

I'm still waiting to here what you would do but feel I will be waiting for
some time.

 

[sqlguru]

No Im not Do you know the difference between a DAL and an ORM or should I
say similarities.

I have an abstraction that allows me to create a DAL/ORM with no reference
to Specific ADO.NET providers. It also allows me to still do database
specific tasks and gain performance benefits associated with specific vendor
providers.

I'm still waiting to here what you would do but feel I will be waiting for
some time.

You clearly don't know what a DAL or ORM is.

Let me explain to you in "beginner/dummy" terms that you can
understand:
ORM maps entities to database tables and automatically takes care of
data operations such as persistence and loading. It works for any
applications and sometimes, any DB vendor. ORM examples are nHibernate
and ORM.NET.
DAL (data access layer) takes care of the data operations, you define
the methods needed. Multiple applications may go through the same DAL
(physical tier).

Also, did you just say that ORMs give performance benefits? Have you
read the performance issues with nHibernate and also how ORM sometimes
generate non-optimized sql? You are an idiot.

 

[Mary Chipman [MSFT]]

Yup, there's always tradeoffs between ease of use and application
complexity when it comes to products and tools like Access, VS or even
SSMS. Unsophisticated users are able to create applications which
later on fail from their own success as they grow in size, scope and #
of users. Tchniques that were fine on the desktop often fail miserably
at the server, which has a steep and unforgiving learning curve. The
original developer (or the person who inherited the app) may not have
the expertise necessary to take it to the next level, so they turn up
on the newsgroups or forums looking for help. Sometimes we "experts"
tend to assume a level of prior knowledge that may not actually exist.

--Mary

 

[Paul]

Lets be straight.

First you never read what I said, and second I asked the
difference/similarities between an ORM and a DAL and you scraped the
surface. You clearly do not understand all you claim.

Secondly, I was talking about provider when I mentioned perfromance benefit,
and If you actually understood anything about Data Access as a whole then
you would understand what I was saying.

Finally you just totaly skiped my question about dbType mapping.

I personally have nothing to prove so If you wish to remain ignorant then so
be it.