Search Results

Often when explaining what an EF query is doing the author will show the (horrid) generated SQL. It doesn't matter what the generated SQL looks like, if it accomplishes its intended purpose. You wi …

In my current job, I carried over this technique, but replaced Entity Framework with Dapper, the micro-ORM that Stack Exchange uses. The queries look almost exactly like the one above. …

The way you make this decision is by optimizing when you need to. There are many scenarios (e.g. a single-record data-entry form) where pulling all of the fields is perfectly acceptable, since you're …

If I have a grid that usually returns 500 records, I assume that for each record it passes on all validations. If my entity has 5 setter validations, than I have passed in 2,500 validations. Only …

Stack Overflow uses a micro-orm. Unlike Hibernate, it's just a thin veneer around SQL queries. Answers to your questions: By writing a SQL query. It can vary from one line of code to about 40. …

Does it mean that if we are using an ORM tool we do not need to design our database like before? You still need a design; it just takes a somewhat different form. …

Your architecture should look something like this: Data source <--> Data source driver <--> CRUD interface <--> Application You'll need one data source driver implementation for each type of data s …

Kinds of objects For purposes of our discussion, let's separate our objects into three different kinds: Business Domain logic These are the objects that get work done. They move money from one checki …

Add a field main_address_id in the User entity or table that holds the ID of the Address record that is the main one. Make that a one to one relationship, if you like. The only solution I have no …

It sounds like your API is too granular; that is, you're retrieving chunks of data that are too small. This code $accountAddress = $sfUserProfile->getCustomer()->getAccount()->getAddress(); woul …

But every ORM still has a mechanism for using raw SQL or stored procedures, or allows you to write such procedures outside of the ORM. …

What you are describing as "Inline SQL" should really be called "string concatenation without parameterization," and you don't have to do that to use a Micro ORM safely. … Well, for the same reasons you would use custom SQL in any other ORM. Maybe the ORM is code-generating sub-optimal SQL, and you need to optimize it. …

Annotations are a nice way to add ORM capability to code that already exists. …

There is much talk about ORM's being storage-independent, under the theory that you might want to change out the underlying data store. In practice this hardly ever happens, and it's a lot of work wh …

ORMs are not intended to completely take over access to your database. Use them for that 80% of code that's CRUD, the stuff that's too tedious to write on your own. Use stored procedures, dynamic SQ …