Found an issue with using Custom Job Names

I'm working on a program that is creating lots of jobs, so I wanted to use custom job names to easily differentiate them.

I am using a combination of a {GUID}|{long}|{string identifier} and it started throwing SQL errors that I traced to the enqueing of the Hangfire job.

I looked through the database, and discovered that the job name is stored in Hangfire.Set.Value. That column has a length of 256, which was fine. The problem comes when the job is added to the Hangfire.Hash table. In there is a column named Key with a max length of 100. Unfortunately, that combines the Set.Value with the Set.Key columns, resulting in a potential length of 350.