Page History

How does Empire-DB handle

...

'' (empty string)?

Empire-DB internally treats all empty strings as null and this behavior is by design.
Some databases accept empty strings as a valid value for a text column, others don’t.
However allowing empty strings is a major reason for many database problems and changing the empire-db code here would have a major impact on existing projects.
We have thought about this a long time ago and we came to the conclusion that empty strings are evil and should be avoided completely.
In fact NULL has a logical meaning of a value not being supplied for a field but what different logical meaning would an empty string have instead?

...

See these projects for more info about connection pools:

• http://c3p0.sourceforge.net^{Image Removed}
• http://commons.apache.org/dbcp/^{Image Removed}
• http://proxool.sourceforge.net^{Image Removed}

Do you have a Scala integration module?

None of us has experience with Scala, but feel free to contribute. This blog post might also help as it points to a project that integrates Scala and empire-db: http://www.acooke.org/cute/UsingScala0.html^{Image Removed}

How do I set the maximum number of rows returned

cmd.limitRows(…)
cmd.skipRows(…) //to set the offset.