I'm currenlty importing blocks into a mysql db (at block 16000 after about 1.5 hours), it'll takes ages (as in: days), but that's ok for me.
One problem I found was with the datadir table:
dirname VARCHAR(500) PRIMARY KEY,
blkfile_number NUMERIC(4),
blkfile_offset NUMERIC(20),
chain_id NUMERIC(10) NULL
)""",
MySql didn't like the VARCHAR(500) primary key. Says it's too long, something about 768 (?) bytes.
Reducing it to 128 helped.
Maybe you should consider using an INT PK here and an index on dirname if you need it? Something within me tells me that having a VARCHAR as Primary Key is somehow bad. Can't substantiate that, but in my own projects, I always use an INT as primary key (I always name it "id", too, but that's another matter). You wouldn't want a VARCHAR(500) as foreign key, would you? That's just wastefull. This is, of course, just a suggestion and I know Abe is currenlty not optimized at all and a change like this will probably be a bitch to upgrade.
Other than that, keep going! I sent my small donation