Implement option to specify any column as primary key

[lafriks]

Partially fixes #244

Still need to implement this into go-rel/sql and probably adapters

[codecov]

Codecov Report

Merging #247 (1d8436f) into master (cbcbfd4) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master      #247   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           56        56           
  Lines         3969      3972    +3     
=========================================
+ Hits          3969      3972    +3     

Impacted Files	Coverage Δ
column.go	100.00% <ø> (ø)
schema_options.go	100.00% <100.00%> (ø)
table.go	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cbcbfd4...1d8436f. Read the comment docs.

[Fs02]

what happens to generated query for each adapter when Primary is set to false?
I'm asking this because for example in mysql, AUTO_INCREMENT need to be defined as a key

[lafriks]

That's really up to the developer on what to define as primary key.

Imho this would still work in MySQL:

schema.CreateTable("audit", func(t *rel.Table) {
  t.BigID("id", rel.Primary(false), rel.Required(true))
  // other fields
  t.PrimaryKey("id")
 })

that would generate:

CREATE TABLE audit (
    id BIGINT NOT NULL AUTO_INCREMENT,
    // other fields
    PRIMARY KEY (id)
);

[Fs02]

but if user doesn't specify t.PrimaryKey("id"), it'll be invalid sql? do you think we should handle that? or just let it error?

[lafriks]

If user on purpose specifies Primary(false) than I don't think library should handle that as that is very database specific, so imho we just let it error

[Fs02]

agree 👍

[Fs02]

LGTM, Thanks!!