We are Turning Over dOOdads to a \"Core Team\"

[mike.griffin]

The source code for dOOdads will be maintained on Tigris -- \"Open Source Software Engineering Tools\". At this point it is extremly difficult to try to both maintain and enhance dOOdads while at the same time work on EntitySpaces and MyGeneration 2.0, which are extremely important in order for us to keep the momentum going. In fact, there are no enhancements to dOOdads in our upcoming MyGeneration maintenance release. EntitySpaces is also hosted on Tigris.

If you want to volunteer send an email to support@mygenerationsoftware.com. But we want to warn you, we're looking for a core group of 6 to 8 hard core dOOdad fans. In your email please list the reasons why you'd like to help and explain your experience with dOOdads. There are lots of tools to help us on Tigris and dOOdad users can post suggestions on the dOOdads Tigris mailing lists, we'll monitor them. MyGeneration will listen in and make comments. All improvements will in the end be made by the core team but approved by MyGeneration for several reasons.

1) We must maintain backward compatibility
2) Changes must be pertitent for ALL DBMS systems (no SQL Server only enhancementes for instance)
3) They must not degrade performance
4) and other things too

Anyway, if you want to help improve dOOdads send an email.

See
http://doodads.tigris.org/

And
http://doodads.tigris.org/source/browse ... k/dOOdads/

[mike.griffin]

Well, some folks have registered, special thanx to those that have, now how about a challenge, this goes out to anyone who is interested.

If you are interested in adding GROUP BY and Aggregates like SUM/AVG and such to the dOOdads Dynamic Query mechanism we'd like to hear from you. We can enhance dOOdads and we can use it for a model when we create the Dynamic Query for EntitySpaces. Any takers?

[dnparsons]

At my experience level, I thought of Mike's GROUP BY challenge more as a puzzle. I'd spend the weekend coding my solution and then compare it to the \"correct\" answer when it was posted. But that was a week ago, and apparently no takers. The Doodads Tigris forum wasn't set up the last time I checked. I may need to embarrass myself and post my code here just to get the pump primed. Doesn't it drive you crazy when a magazine publishes a puzzle and they forget to include the answer in the next issue?

[mike.griffin]

Well, the forums only take like 32k post. Why don't you send me the solution at support@mygenerationsoftware.com and if it looks good you can roll it into dOOdads

[mike.griffin]

Ladies and Gentlemen we have a taker, dnparsons was granted the \"Developer role\" in Tigris last night in the dOOdads system and will be adding some nice enhancements to dOOdads. This is such a great help and allows me to continue to focus on EntitySpaces and tons of things that go on behind the scenes.

We're starting off slowly but this is a good thing ...

[sbc]

It will be hard to improve dOOdads (is it possible for it to be better )

If GROUP BY is implemented that would be very useful. Of course getting it to work for other databases would be hard, so perhaps an exception (NotImplemented) could be raised if someone tried to use it for a database not tested on.

[darin higgins 2]

Hi
I'm not sure if the core team would be interested or not, but I'm in the process of adding heirarchical support to dOOdads (a previous project used a \"rolled my own\" version of such a thing in VB6 and dOOdads with .net is just the ticket to bring it forward)

The plan right now is essentially to interrogate the metadata and automatically add appropriate methods for retrieving related records.

My first step is to just retrieve the related records. That's pretty much going now. I've also got it so that if you don't include a table in your input, any relations to it are skipped, so you don't end up with missing objects and other nastiness.

Next up is to actually handle the \"heirarchical\" part and make all the various CRUD pay attention as one would expect. I've read several of the posts out there concerning this and it sounds... well... sort of straightforward anyway!

So far, I haven't had to modify anything about the base classes (other than add new methods) so everythings nice and compatible.

Finally, I merged the dynamic SQL generation from the Vista templates with the OLEDB and SQL templates and drive it off a checkbox on the UI, so if you want to generate your business entities to use dynamic sql with no stored procs (quite handy for initial testing, among other things), it's just a matter of ticking a checkbox.

I know a lot of this is planned to be covered in EntitySpaces, but it sounds like the plan there is no support for VS 2003, so in the interim, doodads it is for me!

Are those kinds of things of interest?

Either way, keep up the excellent work! doodads honestly rocks. It's the most straightforward of all the OR mapping kits I've seen yet.

Darin

[mike.griffin]

Darin, the last release nearly killed me. My hopes are that this is the last official release of dOOdads for a while. Don't let that stop you though. If what you are doing works out possibly. The last release took nearly 2.5 months of time, if we do another one EntitySpaces and MyGeneration 2.0 are going to come out too late. MyGeneration 2.0 and EntitySpaces are of the upmost importance for us right now to keep forward momentum going.

[adolfojp]

I read that EntitySpaces will be the successor of dOOdads. Will dOOdads be developed any further? Will it remain the main framework of MyGeneration now that EntitySpaces is a commercial product? Should I keep using dOOdads or should I move to another ORM?

[mike.griffin]

Yes, dOOdads is going to be maintained, we are adding SQL stored procedure support for MySQL and even IBM ISeries doodads. I will probably back port a few features from EntitySpaces in fact. I've just been swamped by EntitySpaces, however, it goes live tonight. Watch for a new maintainence build on MyGeneration in about 30 days, with new dOOdads features even ! We are not abandoning dOOdads.

[basio]

I think the general design of doodads should be reconsidered.
think of call LoadAll on a table have 1000000 tuples. I do not really need so.

Also the filters are great but are only accessible after load the whole set of the data.

[mgnoonan]

I think the general design of doodads should be reconsidered.
think of call LoadAll on a table have 1000000 tuples. I do not really need so.

Patient: Doctor, it hurts when I do this.

Doctor: Then don't do that.

Use the WhereParameters to reduce the number of rows brought back (in conjunction with Query.Load()).

Also the filters are great but are only accessible after load the whole set of the data.

Again, use the Query object and the WhereParameters to build a dynamic query and then use Query.Load() to execute it.

http://www.mygenerationsoftware.com/dOOdads/Help/MyGeneration.dOOdads.DynamicQuery.html

[mike.griffin]

The Dynamic Query Mechanism does 10 times more than filter can do and at the SQL Server, Filter is in ADO.NET mechanism we merely expose. And dOOdads is being redesigned http://www.entityspaces.net