So originally I said “I will not use a object-relational mapper.”  My reasons were:

• Overhead
• I don’t mind designing by hand, in fact, I’m fairly good at it
• I don’t have experience with any aside from django’s mapper
• I am not using django (waay too much overhead and wrong toolkit for this.)

I’d looked at the Canonical thing, I think it’s called storm, and it looked decent but in my attempted use of it a month or so ago, I hit upon lack of documentation beyond the tutorial which did not explain some basic things, like “how to get your db design to map.”  Sort of, you know, what a mapper… should do.

I do not feel that sqlalchemy is a good choice because it’s just plain too much overhead.  I don’t really need an ORM.  I need connectivity, and I’ll handle keeping the database in line. I’ve dealt far too many times with software that assumes that if you use a mapper, the database will never get corrupted. Like, you know, 100% of all java db stuff I’ve ever dealt with. In production. Costing me months of time. I hate java; too many “developers” who _can’t._  Those who _can_ develop in java never end up working anywhere near me.

Anyway so with all that background, I said “no” and was busy setting up the db by hand, and – darn it, I went and changed tools. I used to draw stuff up and build the whole design first, then publish; but no I went and was doing it bit by bit using Sequel Pro. No. Bad. It doesn’t … it works but it is NOT a design tool. It is … usable for some stuff I’ve been dealing with at work. With crap db’s designed by people who have no clue. _should have known_ but didn’t think it would be THIS bad.

MySql Workbench worked well but lately it’s just been PANTS. Meaning “Hi, I will crash now!” and such. Also they don’t do ppc. And… yeah.

So in short: I will need to probably write my own ORM type thing after this is over. What I need is a way to define the db directly, quickly, and without having breakage upon a change. And very little overhead.  I want data, put into an object, and I’ll do the push/pull when I need to.

Oh that’s right, another issue with storm was it did not explain in any way, shape, or form how to avoid the problem of persistent connections that needed to be re-attached. Like, if you went to sleep, and they timed out, how to reconnect them the next morning when you were looking at it.

Anyway not publishing this til after. Just saying, this is one of the things that went awry.