Update Scala version to 2.10.0-RC5
Do not advance PositionedResultIterator at the beginning of foreach().

Test case in InvokerTest.testCollections. Fixes issue #81.
Generate proper name for UUID type on PostgreSQL.

Roundtrip test in DataTypeTest.testUUID. Fixes issue #79.

(Excluding the new roundtrip test with bind variables for the TIME type
for now because of an unrelated issue on SQL Server. This will be fixed
in a separate commit.)
Cast bind variables of type TIME to the correct type on SQL Server.

Otherwise they are treated as TIMESTAMP.

Test in DatatypeTest.testTime. Fixes issue #82.
Perform inlining in non-fused generators in fuseComprehensions.

Related to issue #83 but no fix yet. Fusion works correctly now but we
end up with a query shape that is valid in monad comprehensions but not
in SQL comprehensions (a FROM clause referring to a previous FROM clause)
Force comprehension inlining to avoid illegal SQL comprehensions.

When a sub-comprehension refers to a previous generator from an outer
comprehension, force inlining even in the presence of non-trivial
projections. Usually we don't want to inline projections that do more
than just aliasing to avoid code duplication but it's necessary to avoid
illegal SQL comprehension shapes.

Fixes issue #83. Test in NewQuerySemanticsTest.testAdvancedFusion.
Switch to Scala 2.10.0 and revert cross-versioning policy.

The decision has been made that Scala 2.10 will offer compatibility
for all parts of the distribution, even the experimental ones, so we can
cross-publish against 2.10 instead of 2.10.0.
Bump version number to 1.0.0-RC1
Bug fix for Option[Array[Byte]] on PostgreSQL. Closes issue #85.

New test case in DataTypeTest.testByteArrayOption. It turns out that
MS Access (using the standard JdbcOdbcDriver) also has problems with
this type but there is no known work-around for setting a LONGBINARY
value to NULL, so we add BasicProfile.capabilities.setByteArrayNull for
this feature and disable it in AccessDriver.
Add some new test cases:

- Returning result sets wider than 22 from Plain SQL queries
  (PlainSQLTest.testWideResult)
- Abstracting sortBy and map into a utility method
  (MiscTest.testSorting)
- Testing the Case feature (MiscTest.testConditional)
Use NumericTypeMapper for BigDecimal and Short. Related to issue #24.

A completely revamped DataTypeTest.testNumeric can test the different
numeric types individually while ensuring they actually have a
NumericTypeMapper and only running tests for supported types on each
driver.

This is the first test for BigDecimal so it uncovered some problems.
We need to pick an arbitrary default scale and precision because they
differ wildly across database systems. I chose 21,2 to get the full
scale of scala.Long plus 2 extra digits of precision after the decimal
point. SQLite and Access do not support decimal types, so there is a
new capability BasicProfile.capabilities.typeBigDecimal to reflect this
restriction.

BasicProfile.capabilities.all was also missing some previously introduced
capabilities (enabling these capabilities and thus the associated test
cases fortunately did not turn up any regressions).
Improved documentation:

- A chapter on Slick Extensions
- More lifted embedding features: Deleting, Inserting, Updating,
  Query Templates, User-Defined Functions and Types
- Structured list of supported primitive types
- Correct slick artifact spec in gettingstarted.rst
- Better auto-generated names for inner classes in apilinks.py
- Link to ScalaQuery for Scala 2.9 in introduction.rst (fixes issue #68)
New test case for using more than 22 columns in lifted embedding
Change groupId to com.typesafe.slick and version to 1.0.0-RC2
Change base package for sample code to com.typesafe.slick.examples.

Doc snippets are now going into com.typesafe.slick.docsnippets.
Merge branch '1.0'

Conflicts:
	build.sbt
	slick-testkit/src/main/scala/com/typesafe/slick/testkit/tests/DataTypeTest.scala
	slick-testkit/src/main/scala/com/typesafe/slick/testkit/tests/MiscTest.scala
	src/main/scala/scala/slick/compiler/Relational.scala
	src/main/scala/scala/slick/driver/AccessDriver.scala
	src/main/scala/scala/slick/driver/BasicProfile.scala
	src/main/scala/scala/slick/driver/JdbcTypesComponent.scala
	src/main/scala/scala/slick/driver/PostgresDriver.scala
	src/main/scala/scala/slick/driver/SQLiteDriver.scala
	src/main/scala/scala/slick/lifted/TypeMapper.scala
Add codeGen phase to generate SQL code within the AST.

This allows us to build more complex trees that contain client-side
mappings on top of SQL. Later on we should be able to use this as a basis
for nested collections and distributed queries, both of which require
similar mechanisms.

Concrete instances of codeGen are created by the drivers and appended
to the driver's common QueryCompiler configuration to obtain different
compilers for the different kinds of statements (select, update, delete)
that can be built this way.

This initial commit does not generate client-side mappings yet because
not all uses of the query AST and the old code generator model have been
adapted to use the codeGen phase.
Remove OldTest.

Some queries there that are actually useful are moved over to
NewQuerySemanticsTest and executed against all databases (instead of
merely checking that they compile without throwing an Exception).
Pass fully compiled ASTs to invokers and executors.

We also enable the generation of ResultSetMapping nodes in the
hoistClientOps phase. The invokers and executors just throw them away for
now and use the old ValueLinearizer which gets passed in as a
separate argument.
Replace ExtendedProfile and ExtendedDriver with deprecated type aliases.

We keep these around for one more release for improved source
compatibility with 1.0.