Possible bug in sybase-db?

Zeev: I just finished coding up a patch to sybase-ct to add charset support. I want to put it through a little more testing before I apply it, but in the process, I found what appears to be a bug in the db extension, and you seemed like the right person to talk to. It all comes from "hashed_details_length". If they specify a charset, then hashed_details_length will be one byte too short...there is no space allocated for the _ seperator in the hashed_details. So I followed what seemed to be the conventional wisdom, and added one byte to all cases, and added an extra _ at the end of cases 1-3. Is this the correct way to do this? Was this even a bug, or are we safe anyways? I attached the patch so you could take a look at it.