schemaspy VS Testcontainers

You might try https://schemaspy.org/ - it generates a website with ER diagrams that only go one or two relationships out, but they have clickable table names to get to the next diagram

I had the same problem when i started my job. I used SchemaSpy to generate an html with all of metadata and ERD diagrams as a reference point. Then i used dbt to connect to the database and used dbt to document the table and column that i have worked on. It takes time to document but it's worth it if you company don't have your database documented yet.

SchemaSpy is a standalone application that connects to the database, scans its tables and schemas, and generated nicely composed HTML documentation. You can check out an example sample by this link but I'm showing you just one screenshot to clarify my point.

I like https://schemaspy.org/

I like the diagrams and reports SchemaSpy generates. If you are using a DBMS that allows setting comments to tables, views, columns (and other objects), those will be included and that makes those reports even more helpful

https://schemaspy.org/ creates nice looking diagrams.

except the parent is wrong (at least the Java impl). see:

https://github.com/testcontainers/testcontainers-java/blob/m...

https://github.com/testcontainers/testcontainers-java/blob/m...

> I wonder if Rancher Desktop, et al, works with testcontainers.org?

I don't use testcontainers myself, but it looks like as long as you are using Rancher Desktop >= 1.0.1 you should be just fine.[1]

[1] https://github.com/testcontainers/testcontainers-java/issues...

Thanks for the feedback. You are right, and there are some other mock-up alternatives as well, a good one for developers https://testcontainers.com/

In this article, we will explore how to use Testcontainers and Exposed, a lightweight ORM framework for Kotlin, to create a controlled environment for testing MySQL Database operations.

Unfortunately, it still remains hard to use Testcontainers because of how wedded it is to junit4, five years after the release of junit 5. https://github.com/testcontainers/testcontainers-java/issues/970

Finally, we put the directory with generated contents (HTML, CSS, JS) into a tarball. Testcontainers library allows to copy files from a container to the OS but not directories. That’s why we need an archive inside the SchemaSpy container.

This repository provides a BuildImageTest that uses the buildpack to create a native image. It then tests the native image, using Testcontainers and JUnit. Building the native image with AOT processing, as part of a test, takes minutes not seconds, and should not be part of normal "inner loop" development. So the BuildImageTest is in a separate sourceSet and can be executed independently. This is a very powerful pattern, that I'm just getting started with. I would love to hear your thoughts on this pattern or other alternatives to it.

The list goes on. Check out the full list of Testcontainer modules.

Test-Container Java

TestContainers looks Java specific... or are you talking about something else?