Support Forums: Message List - ORM and the misleading DAO pattern

Pros

Thu, 24 Mar 2011 22:37:57 -0400

I am not sure if DAO layer would bring advantages to software developers. As stated, its pattern does not isolate well and might add more concerns. Perhaps it is worth a try. web hosting

High PR Backlinks

Tue, 01 Feb 2011 00:05:53 -0500

Hello friends i am expert engineer of SEO company so i would like to suggest you that i found a company that provides a High PR Backlink on cheapest price.

...

That's an ugly design Re: ORM and the misleading DAO pattern

Tue, 02 Oct 2007 04:01:14 -0400

Yes, you are obviously missing something. In wrapping the underlying layer as an API (they called it DAO design pattern), you said that converting from JDBC to ORM will render the DAO useless. The thing is that, sometimes we also need to access data...

Re: ORM and the misleading DAO pattern

Wed, 07 Jun 2006 09:33:03 -0400

Hi!...

performance Vs. comfort

Fri, 02 Jun 2006 07:32:42 -0400

I'm surprised that nobody has mentioned performance's view so far. ...

Re: ORM and the misleading DAO pattern

Mon, 29 May 2006 08:46:26 -0400

...but I think the "real" solution to this is not to use the DAO-pattern at all - we shouldn't have to deal with persistence explicitely, our "domain objects" should simply be persistent, end of discussion.

...

Re: ORM and the misleading DAO pattern

Sun, 28 May 2006 11:04:24 -0400

Hi all,...

Re: DAO means different things to different people

Fri, 26 May 2006 19:48:08 -0400

All we want is an "Abstraction" to Data Access......

DAO antipattern?

Fri, 26 May 2006 05:30:00 -0400

"Isolating logic and persistence from each other. Whether a modern ORM tool can fill the DAO need is an application design question. For many applications, an ORM tool can be used as the DAO layer."...

Remember that you have choices

Fri, 26 May 2006 05:14:40 -0400

The reality is that sometimes DAOs are the most appropriate way to access a database, sometimes a persistence framework is, sometimes services are, and sometimes it's even best to simply embed SQL code in your business objects. The Agile Data method...

Re: DAO means different things to different people

Thu, 25 May 2006 07:27:43 -0400

Correction: I horribly misspelt "redundency". Paul.

DAO means different things to different people

Thu, 25 May 2006 07:25:22 -0400

Part of the problem with any "DAO" disscussion is that there are two flavours of the pattern in common use:...

Re: ORM and the misleading DAO pattern

Wed, 24 May 2006 12:01:35 -0400

It's a specifically confusing example because he used Object, implying it works for anything, rather than ClassX, meaning it's class specific. But change it to "ClassXDAO.update(ClassX cx, Connection conn)", and it basically...

Re: ORM and the misleading DAO pattern

Wed, 24 May 2006 11:56:50 -0400

It's a specifically confusing example because he used Object, implying it works for anything, rather than ClassX, meaning it's class specific. But change it to "ClassXDAO.update(ClassX cx, Connection conn)", and it basically...

Re: ORM and the misleading DAO pattern

Wed, 24 May 2006 11:07:45 -0400

I still don't get it. What if I DO want my setFirstName() to take effect right away? If calling save() does no-op, does ending the current session the only way to make the persistence happen?

...