[DOCS-9294] Documentation for BI-762: Column types should emulate MySQL types Created: 09/Nov/16  Updated: 26/Jan/18  Resolved: 26/Jan/18

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Emily Hall Assignee: Steve Renaker (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
Participants:
Days since reply: 7 years, 14 weeks ago

 Description   

Engineering Ticket Description:

Given this DRDL:

schema:
- db: test
  tables:
  - table: numeric
    collection: numeric
    pipeline: []
    columns:
    - Name: _id
      MongoType: bson.ObjectId
      SqlName: _id
      SqlType: varchar
    - Name: d
      MongoType: bson.Decimal128
      SqlName: d
      SqlType: decimal128
    - Name: f
      MongoType: float64
      SqlName: f
      SqlType: float64
    - Name: i
      MongoType: int
      SqlName: i
      SqlType: int
    - Name: l
      MongoType: int64
      SqlName: l
      SqlType: int64
    - Name: m
      MongoType: number
      SqlName: m
      SqlType: numeric

the column types in the information schema look like this:

mysql> show columns from numeric;
+-------+------------+------+------+---------+-------+
| Field | Type       | Null | Key  | Default | Extra |
+-------+------------+------+------+---------+-------+
| _id   | varchar    | YES  |      | NULL    |       |
| d     | decimal128 | YES  |      | NULL    |       |
| f     | float64    | YES  |      | NULL    |       |
| i     | int        | YES  |      | NULL    |       |
| l     | int64      | YES  |      | NULL    |       |
| m     | numeric    | YES  |      | NULL    |       |
+-------+------------+------+------+---------+-------+
6 rows in set (0.02 sec)

While we haven't seen problems with any tools as yet, it would be better if the column types reported here are named more similarly to the MySQL types.


Generated at Thu Feb 08 07:58:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.