Talk:Active record pattern

From Wikipedia, the free encyclopedia

I think enterprise applications shouldn't link to java enterprise applications. These techniques are really applicable to more, and the link is misleading. ~JWHPryor

I don't think LINQ is an implementation of Active Record. It seems to just add a veneer on top of sql statements, rather than creating an maintaining a whole object.

It definitely is not. Besides, it was just thrown in for no reason. I'm removing it. --AndreFillipe 11:00, 4 January 2007 (UTC)

What about Enterprise Java Beans - don't they fit the bill?

Perhaps we could have a section talking about the pros/cons of having your entity domain classes aware of their storage mechanism?

By what criteria are some of the open source implementation links allowed to remain and others removed? -68.58.169.229 (talk) 04:48, 25 January 2008 (UTC)

Hu12 please explain why the references to Rails active record and the C++ implementation from butterfat were remove? —Preceding unsigned comment added by 24.214.173.82 (talk) 05:00, 25 January 2008 (UTC)

[edit] some thoughts

The "pseudo-code" is valid JavaScript, although I don't know of any implementations of Active Record in JS.

I'm making the following changes: pointing out that it's common in software that accesses databases (enterprise or no), but acknowledging Martin Fowler's "Patterns of Enterprise Application Architecture" as the source of the name.

Kragen Javier Sitaker (talk) 20:38, 10 April 2008 (UTC)