summaryrefslogtreecommitdiff
path: root/test/dialect/mysql/test_reflection.py
diff options
context:
space:
mode:
authorMike Bayer <mike_mp@zzzcomputing.com>2022-08-09 09:50:57 -0400
committerMike Bayer <mike_mp@zzzcomputing.com>2022-08-09 09:50:57 -0400
commit7e442cd0a9341ac828b4c4820818ad80ad9200fa (patch)
treec8fc1965ee21856a47b5020f93dafe974899fc94 /test/dialect/mysql/test_reflection.py
parentac1d775d862e62561effcce54462f687dd79b8bb (diff)
downloadsqlalchemy-7e442cd0a9341ac828b4c4820818ad80ad9200fa.tar.gz
improve names for datatypes section
Continuing along #8362, if we look at the document here without "this is the same text I've read for 14 years", we begin to see that the title "Column and Data types" makes no sense at all, is there a "column type" and a "Data type"? I guess what I was thinking at that time is that a type can be placed on a Column, or it can be used whenever you have, you know, "data". The phrase "SQL expression" wasn't discovered yet. "SQL Datatype" is not spectacular but at least it's one term. the new intro then is focused on the hierarchy layout so let's name it that. not amazing, but better than the duplicate name that made no sense before. Fixes: #8362 Change-Id: Iab37ef5605ec55f30284ac9a98bf7246f736675d
Diffstat (limited to 'test/dialect/mysql/test_reflection.py')
0 files changed, 0 insertions, 0 deletions