Can't declare a squeryl index on a MandatoryTypedField unless it is of type Int
on(table)(t => declare(t.column is indexed)) results in:
type mismatch;
[error] found : org.squeryl.internals.Indexed
[error] required: Int
See: http://groups.google.com/group/liftweb/browse_thread/thread/7236b335f4e017c0/f9fa68d4640c3937#f9fa68d4640c3937
type mismatch;
[error] found : org.squeryl.internals.Indexed
[error] required: Int
See: http://groups.google.com/group/liftweb/browse_thread/thread/7236b335f4e017c0/f9fa68d4640c3937#f9fa68d4640c3937
Leave a comment
(In revision:39e9d8af5205fc9cd27b8ce29487b008fa4554f5) Bugfixes for squeryl-record: Index declaration and implicit conversions for fields of objects that are not retrieved in the current query
Closes #840
Closes #843
Added the traits SquerylRecordNumericalExpression and SquerylRecordNonNumericalExpression that are now mixed into the expressions returned
from the implicit conversions. With this trait, defineAs can be used instead of "is", which is ambiguous for record fields.
Moreover, the case that FieldReferenceLinker.takeLastAccessedFieldReference returns None is now handled correctly in the implicit conversions.
Added some test cases for showing that "defineAs" can be used instead of "is" in the schema declaration and that fields from
earlier retrieved records can be used in other expressions now.
There were also issues with Timestamp fields, which are resolved by using Timestamp instead of Date in the implicit conversion for DateTimeField.
Branch: master
Closes #840
Closes #843
Added the traits SquerylRecordNumericalExpression and SquerylRecordNonNumericalExpression that are now mixed into the expressions returned
from the implicit conversions. With this trait, defineAs can be used instead of "is", which is ambiguous for record fields.
Moreover, the case that FieldReferenceLinker.takeLastAccessedFieldReference returns None is now handled correctly in the implicit conversions.
Added some test cases for showing that "defineAs" can be used instead of "is" in the schema declaration and that fields from
earlier retrieved records can be used in other expressions now.
There were also issues with Timestamp fields, which are resolved by using Timestamp instead of Date in the implicit conversion for DateTimeField.
Branch: master