Re: Alternative to Dynamic SQL?

Tech-Archive recommends: Fix windows errors by optimizing your registry

Yeah so instead of gathering application requirements, doing a
functional analysis, design, use cases, prototypes...you go straight
into development first.....because you know, client requirements are
always possible in "agile development" no matter how non-feasible it
maybe. Remember, failing to plan is planning to fail.

You also have no idea what OOP means. The "tests" you are talking
about are use cases and do not fall under tests at all. Go back to
software engineering 101.

On Jun 2, 10:49 am, "mark4asp" <mark4...@xxxxxxxxx> wrote:
sqlg...@xxxxxxxx wrote:
RDMS are based on relational models and sets, it's not supposed to
have OOP properties like inheritance etc. Persistance is one part of
the application?????

Which is exactly why its a problem. It's not that I have a silver
bullet to solve the problem but I can see that there is a problem.

Do you really write the application layer first
than the data model?

That's exactly what many people are doing nowadays. It's what I'd do if
I were writing a new application. It's not what I've been taught to do;
nor what I've done in the past.

Do you know what CMMI is (you know, app requirements, process
planning, functional reqs)????

I'm all for process improvement. Process improvement is also the aim of
Agile and test-first.

If learning CMMI could turn me into a better developer I would've done
it years ago. I'm just not convinced by any of these big processes. Too
many big failures.

No, you don't know any of that because you're a entry level programmer
using ORMs thinking that it is the future.

I'm definitely not 'entry level'.

Many of the people I meet using ORMs have been coding for decades. The
particular tendency they generally follow is one of test-first agile
development. To do that right you can't really get away with being
'entry level'. By and large, you need to understand OO priciples, OO
design and patterns and to discipline yourself to always write tests
before your implementation.  Not entry level at all.

That's a trite line of argumentation you employ, bullying by
denegrating when you don't really understand why someone is putting
forward an alternative.

.