Just sent this to Fran, maybe you can help too
Andrew Clancy
I am struggling to convincing my (architect) colleagues that O/R mapping,
and your product, is something we cannot ignore as a tool that could save us
mountains of work (we're currently moving a largish company into the .Net
arena so every project is new at the moment), and there is no codegen at
all.
Here's a couple of my problems, which maybe you can help me with:
1. One of my colleages only agrees with something if it is written in msdn
or somewhere formal on microsoft.com (and not a blog), but I've sent him
over the ObjectSpaces docs so hopefully he'll come round soon. But, if you
know of any other formal docs in recognised sites (eg. asp.net) that might
help me, please send 'em over!
2. The sproc vs d-sql arguement is going to be another fun battle - we have
that security model where webservers can only have access to sprocs, and I
think this is written into some of our contracts with banks. I'm hoping to
get around this with an arguement that internal/admin/CMS systems dont need
this level of security, so at least then we only have to code up (or
codegen) the CRUD. Again, if theres any formal docs out there which can back
me up I'd appreciate them!
3. That same colleague has introduced us to custom entities & collections,
which is a good thing. He suffers fromt NIHS though, and wants us to write
our own codegen though, as at first glance the custom entities output by
LLBLGen are 10 times the size of ours, and Wilsons ORM seems like it would
be easy to write (again, at first glance). We can build a product without
ORM, and the codegen would be simple. But if I do manage to convince them
(and myself!) that ORM is going to save a lot of time & hassle, then how do
(or maybe the question is should) I convince them that ORM apps like yours
are complex enough to waste a massive time in development on (again another
formal 3rd party doc would be great!), and that yours is the way to go over
the rest (without them using it, they arent even going to try at the
moment).
. I have one small question for my own understanding first though
Over on http://www.theserverside.net/news/thread.tss?thread_id=29071
you've written this piece of code. How is this going to save me time over
the folloing much smalled & more readable SQL?
EmployeeCollection employees = new EmployeeCollection();
IRelationCollection relations = new RelationCollection();
relations.Add(EmployeeEntity.Relations.OrderEntityUsingEmployeeID);
relations.Add(OrderEntity.Relations.CustomerEntityUsingCustomerID);
IPredicateExpression filter = new PredicateExpression();
filter.Add(PredicateFactory.CompareValue(
OrderFieldIndex.OrderDate, ComparisonOperator.Equal, _givenDate));
filter.Add(PredicateFactory.CompareValue(
CustomerFieldIndex.Country, ComparisonOperator.Equal, "Austria"));
employees.GetMulti(filter, relations);
SELECT *
FROM Order
INNER JOIN Employee
ON Order.EmployeeID = Employee.EmployeeID
INNER JOIN Customer
ON Customer.CustomerID = Order.CustomerID
UnquaLe
if u are a Company u have to use a product. U can use VERSANT OPEN
ACCESS or
EntityBroker.
If u are developing ur project with TransactionModel it fails..
You need a domain model.. I think you have DomainModel for your
projects.. so it is really easy to map your domain objects to Database.
ObjectSpaces is good becouse it is MS product. but Nobody doesnt know
when it will release.. I think it will release with Longhorn.
But I would prefer a ObjectOriented DB. ;)