I have added an experimental plugin that uses the same schema as pushpool I think.  I really don't feel like setting up a pushpool server to verify things match up 1:1 though.  If someone doesn't mind dumping their shares table to get better sample data I can make sure it is behaving as expected.  It doesn't support the "reason" column because I would need to modify WorkUnit a bit and a lot of the signaling I use rather then just onReject or onAccept.  I got one exception where the data/work was cut off but it should be 256 characters long.  Eh.

The plugins use storm for the ORM (to connect to mysql you need MySQL-python).  I haven't used it before so it was interesting and hacky with omg unicode requirement.

I need to finish up my schema backend as it should consume much, much less space/resources SQL wise then pushpool.  But I was a bit uncertain how to maintain parity with some of the pools like like displaying Mh/s.  Because I want to only sync shares every few minutes.  But it is not guaranteed it would be every x minutes.  Also there is the trick of counting shares delta time.  Do we opt just to resume and keep incrementing shares and update the table entry, or do we insert the shares for the given work into a new row.  Do we need to track rounds in the shares?  Ughghg

Oh well I will sleep on it a bit.  Also this post made no sense whatsoever but I am bored and chatty.