I don't think we should remove it. It's a lot easier to use and covers most use cases (how often do you need named or composite PKs?), so it should be the default

cvogt <notifications@github.com> wrote:
>> @@ -54,6 +73,11 @@ abstract class AbstractTable[T](val tableTag: Tag,
>val schemaName: Option[String
>>      new ForeignKeyQuery[TT, U](Filter.ifRefutable(generator,
>q.toNode, fv), q.unpackable, IndexedSeq(fk), q, generator,
>aliased.value)
>>    }
>>  
>> +  /** Define the primary key for this table.
>> +    * It is usually simpler to use the `O.PrimaryKey` option on the
>primary
>
>Maybe we should deprecate O.PrimaryKey for api uniformity or at least
>not use it in the docs?
>
>---
>Reply to this email directly or view it on GitHub:
>https://github.com/slick/slick/pull/238/files#r7276713

-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.