Using TestContainers to compare database properties #9252
beargiles
started this conversation in
Show and tell
Replies: 1 comment
-
Database Metadata Comparison**This is prelimary work - it's only public for discussions during my job search ** This repo contains a simple app that launches a large number of databases (via TestContainers), The next big step is a comparison of the standard types. I know from prior work that that will be... interesting. Here's the current output. Product Summary
Limits
Boolean properties
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
A quick note of a tool I developed a while back to compare database properties using TestContainers. The process is pretty straightforward:
Connection#getDatabaseMetaData()
In this case I'm comparing some of the Big Four, some custom cloud databases (which I'm trying to perfect), and two hack jobs so I can also include H2 and SQLite since the latter two are so widely used when you don't need to power of a full database server.
It could also be used to compare features of different versions of the same database. Most of the changes are transparent at this level - but not all.
The main goal is to compare the basics like limits, e.g., how large can a text field be? Is it "catalog", "schema", or both. (I know at least one database uses catalog, schema, and table names.)
It can also be used as a quick reminder of things like 'int' actually means. It's probably 32 bits... but are you sure? Maybe it's 64 bits on a particular database.
Finally, it's not implemented yet but I also wanted to expand on the list of functions, etc., so you could tell at a glance whether a particular function is available.
(Sample output below. I don't know why it appears twice.)
Beta Was this translation helpful? Give feedback.
All reactions