Bogdan Popa

Hey, Thanks for the contributions! Can you also add a note in the README about this? I'll merge it in afterwards.

It depends on what you'd like the constraints to do. I'd say constraints to enable things like lazy loading/automatic relationships are out of scope, but if you're just looking to...

I don't personally use MySQL so any help adding it would be appreciated! As for pointers: * I'd start by adding a [dialect](https://github.com/Bogdanp/deta/tree/b3d6824585e76f0d24583b70fc1bd9e60e61372b/deta-lib/private/dialect) that, like the other two, uses the...

I see your point, though it seems wasteful to have to do that (especially with databases that don't support `RETURNING`) by default given that tables with triggers are the exception...

I haven't thought much about this yet, because I mostly use deta in private applications. I agree that a `defschema` would be neat. I don't think I'll get to that...

I think the issue is that you haven't prefixed `github-id` with `gu` in your query. This works: ``` (lookup db (~> (from github-user #:as gu) (where (= gu.github-id 123)))) ```

Yes, I think we can detect cases like this, where the identifier contains a dash. However, I don't think this can be detected in general.

> By analogy `(where (= github-id 123))))` ought to work too. I would say it's the reverse. ```racket (= id ,id) ``` IMO, this and any use of an unqualified...

> The easiest solution would be to have things continue working as they do now and just replace `-`s with `_`s within identifiers. I spoke too soon and didn't take......

@andrewgy8 yup, e-mail is fine.