-
Notifications
You must be signed in to change notification settings - Fork 36
Schema dumper does not recognize all Spanner specific features #88
Copy link
Copy link
Open
Labels
🚨This issue needs some love.This issue needs some love.api: spannerIssues related to the googleapis/ruby-spanner-activerecord API.Issues related to the googleapis/ruby-spanner-activerecord API.priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Description
Metadata
Metadata
Assignees
Labels
🚨This issue needs some love.This issue needs some love.api: spannerIssues related to the googleapis/ruby-spanner-activerecord API.Issues related to the googleapis/ruby-spanner-activerecord API.priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
The schema dumper does not recognize all Spanner-specific features. At least the following features seem to be problematic:
allow_commit_timestamp: trueis not generatedTIMESTAMPcolumns are registered with typetime