In general, the SqlBuilder package has strived to use ANSI SQL92 syntax only (with a few minor deviances).
As of the 2.1.1 release, SqlBuilder supports a syntax customization framework, with a few database specific constructs currently built-in.
As of the 2.1.2 release, some ANSI SQL99 features have been added (newer standards classes will be marked as such, e.g. "SQL 99").
Well, that's not really a question, but we get where you're coming from. Pretty much every method has a "custom" counterpart which can be used to inject pretty much any custom syntax you want. The queries use different converters to interpret the arguments to these methods. In most cases these converters "do the right thing", but if they do not, you generally just need to wrap your custom object in a CustomSql object.
Probably because you're missing a jar that SqlBuilder depends on from your classpath. Take a look at the dependencies list. The "compile" and "runtime" dependencies are necessary for using SqlBuilder in your application. One great place to track down these dependencies is in the Ibiblio Maven Repository.
HMS is a small company located in suburban Philadelphia. Using proprietary matching and consolidation software, HMS scientifically manufactures the most comprehensive and accurate healthcare data sets in the market today.