yooooooooo this is sick

One of my favorite parts of rails is schema.rb which acts as a canonical in-code representation of the database, which makes checking "how is this all connected?" as simple as reading a single file (instead of sending multiple queries in a database repl and figuring it out yourself). This pretty neatly solves that problem if you use a wrapper around a migration library (like migratus)

yes! That’s something I miss from rails too. I really like that idea

Is it possible to use clojure.java.jdbc? We've not begun switching over yet

you can use both side by side without having conflicts AFAIK

That's true

@U0AQ1R7FG noice! would be great to be able to https://github.com/donut-party/dbxray/blob/1d84500c9693ab806414128905aae844614675dd/src/donut/dbxray.clj#L31 a schema name

hmm yeah xray could take an optional second argument, an adapter config that’s merged with the default

@U0541KMAZ ok I threw that in without really checking it but I think it should work 😅

amazing work!

Love the name!

> Is it possible to use clojure.java.jdbc? We've not begun switching over yet We have both in our codebase at work. We create a HikariCP connection pooled datasource from our db-spec hash map at startup and then pass {:datasource cpd} around our code as db-spec. That works as-is with c.j.j and, since next.jdbc 1.2.790, that also works as-is so it's easy to use the two together while you migrate. Prior to that, when we called next.jdbc we passed (:datasource db-spec). Just bear in mind that c.j.j's default is rs/as-unqualified-lower-maps in next.jdbc unless you also change the code to handle the results (which we mostly did not do). So you can easily switch one call at a time.

@U0AQ1R7FG yep, https://clojurians.slack.com/archives/C06MAR553/p1667576944769159?thread_ts=1667573312.021829&cid=C06MAR553 to create the schema! https://github.com/donut-party/dbxray/blob/a3bd2cb391e040ed0d5d51d0374d387d26a8aef1/src/donut/dbxray/generate/malli.cljc#L18 might need to only take the “`table-name`” once though?

=> (csk/->PascalCaseSymbol :foo)
Foo
=> (csk/->PascalCaseSymbol :foo :foo)

Execution error 
No value supplied for key: :foo

whoops thanks, good catch!

thank you @U11EL3P9U and @U0PUGPSFR 🙂

woooo man this is awesome!

😊 thanks! @mpoffald helped me with it. I hope it’ll be useful for people!

So cool! One of the things which was on my list of "when I get to it or get angry enough" Thank you!

Tiny suggestion regarding malli schema: emit a registry and not def forms?

hmm what do you think of having both? generate-defs generate-registry

I certainly see no reason to object 🙃

Now imagine plugging this in to clerk, portal, etc 👀

You made a db explorer, buddy. Or at least the building blocks for one. Congrats 🙂

You can also write a db client. A desktop client. With membrane!

I think that would be super dope!

You can use https://github.com/donut-party/dbxray to help you get started with datapotato - dbxray can generate the clojure specs / malli schemas you need to generate data, plus the “potato schema” datapotato needs to handle entity hierarchies

Really went looking for a "Because I'm a potato" quote in the readme 😄