p

org

squeryl

package squeryl

Ordering
  1. Alphabetic
Visibility
  1. Public
  2. All

Type Members

  1. trait EntityMember extends AnyRef
  2. class ForeignKeyDeclaration extends AnyRef

    ForeignKeyDeclaration are to be manipulated only during the Schema definition (this is why all public methods have the implicit arg (implicit ev: Schema))

  3. trait IndirectKeyedEntity [K, T] extends KeyedEntity[K]
  4. trait KeyedEntity [K] extends PersistenceStatus

    For use with View[A] or Table[A], when A extends KeyedEntity[K], lookup and delete by key become implicitly available Example :

    For use with View[A] or Table[A], when A extends KeyedEntity[K], lookup and delete by key become implicitly available Example :

    class Peanut(weight: Float) extends KeyedEntity[Long] val peanutJar = Table[Peanut]

    Since Peanut extends KeyedEntity the delete(l:Long) method is available

    def removePeanut(idOfThePeanut: Long) = peanutJar.delete(idOfThePeanut)

    And lookup by id is also implicitly available :

    peanutJar.lookup(idOfThePeanut)

  5. trait Optimistic extends AnyRef
  6. trait PersistenceStatus extends AnyRef
  7. trait PrimitiveTypeMode extends QueryDsl
  8. trait Query [R] extends Iterable[R] with Queryable[R]
  9. trait Queryable [T] extends AnyRef
  10. trait ReferentialAction extends AnyRef
  11. trait Schema extends AnyRef
  12. class Session extends AnyRef
  13. trait SessionFactory extends AnyRef
  14. class StaleUpdateException extends RuntimeException
  15. class Table [T] extends View[T]
  16. class View [T] extends Queryable[T]

    This class can be used for read only tables or (database) views for an updatable view, or table use Table[T]

Value Members

  1. object DummyEnum extends Enumeration
  2. object PrimitiveTypeMode extends PrimitiveTypeMode

    This factory is meant to use POSOs (Plain old Scala Objects), i.e.

    This factory is meant to use POSOs (Plain old Scala Objects), i.e. your object use Scala's primitive types to map to columns. This can have a significant performance advantage over using object types i.e. a result set of N rows of objects with M field will generate N * M objects for the garbage collector, while POSOs with primitive types will each count for 1 for the garbage collector (to be more precise, String and Option[] fields will add a +1 in both cases, but a custom String wrapper will also add one ref, for a total of 2 refs vs a single ref per string column for the POSO). This lightweight strategy has a cost : constants and object field references cannot distinguish at compile time, so this mode is less 'strict' than one with a CustomType

  3. object Session
  4. object SessionFactory

Ungrouped