Michael Italia

Wrap the jdbc metadata call so that it is easy to check if a table exists.

For queries like count(), sum(), min(), etc… where only one value is returned, there should be a convenience function that wraps a single row select and returns a simple Option[Any]...

As a convenience it would be good to have a single row select for queries that are guaranteed to return only one row (e.g. select by id)

In general we have a mix of semantics in use when sql methods are called. They should be unified as follows: If a method can return something (e.g. a count,...

The SqlBackend is more java-like than Scala-like. It probably should use the Option type for connections instead of nulls. That being said, it may be necessary to hold off on...

In order to allow complex tasks a SqlStore should expose an execute method that passes SQL to the backend without the user having to use the API.

DataRows are immutable so DataRow needs the set methods (plus, minus, etc...)

As it stands, DataTables have fixed .next and .hasNext functions. Ideally, an advanced user (or someone doing work on the internals of DataExpress) might benefit from a constructor that allows...

When getting JDBC types from the database (e.g. for creating a table based off a query), DataExpress needs to use the metadata to ascertain what the type is. In most...