Norm 2.0.0

It is my pleasure to announce that norm with the coming version of 2.7.0 is now ready and eagerly awaiting nim 2.0 ! It took a bit, not the least of which included making a fork of `ndb` that is now called `lowdb` with changed testing-infrastructure-setup, to do so as the relocation of db_commo

Norm 2.0.0

The first Norm version with Nim 2.0 support is officially released: 🍾

Norm 2.0.0

Recently `juancarlospaco` has written a testament docs which is more detailed:

Norm 2.0.0

It's great, just missing a good tutorial. There's [this nice intro](https://dev.to/xflywind/how-to-use-testament-in-nim-1l0h) but it covers only the basics. I feel that testament is large enough to deserve a series of articles or a book.

Norm 2.0.0

So nice that testament is finally seeing some adoption. :-)

Norm 2.0.0

Norm 2.2.1 has just been released. The biggest feature in this release is [manual foreign key management](https://norm.nim.town/#manual-foreign-key-handling). You can now omit Norm's automatic foreign key handling to optimize JOIN queries. The cost is that you'll have to fetch related objects m

Norm 2.0.0

I'm happy to announce that Norm 2.2.0 has just been released. This is quite a fat release, fixing a couple of nasty bugs: * JOINs have been reimplemented allowing to have fields with the same names in related models. That fixes the issue reported a few posts higher:

Norm 2.0.0

Boy oh boy, did that bug fix turn into a major version bump with an API change: Thanks for reporting the issue! Apparently, the way `JOIN` statements were generated was just broken.

Norm 2.0.0

I really appreciate the detailed explanation, this makes a lot of sense. Love the template macro, just another example of Nim providing the power to make life easier :) Reported an issue for the foo1/foo2 problem!

Norm 2.0.0

There are a few unrelated topics here, I'll cover them one by one. **1\. One-to-many in Norm** > . But it seems a little counter intuitive to me. If a purchase is composed of > subpurchases, my natural approach would be to define a purchase object with a > seq of subpurchases. But if I understa

Norm 2.0.0

Thanks for the quick response! I've been looking through the linked project, I see a similar relationship between customer and subcart. But it seems a little counter intuitive to me. If a purchase is composed of subpurchases, my natural approach would be to define a purchase object with a seq of

Norm 2.0.0

Duplicating my response from the issue: I've created a demo app that I use to test Norm and Norman more or less olin the wild. It has an example of one to many relation: Here, a full purchase is composed of subpu

Norm 2.0.0

This type definition is not enough to debug your case. Please provide the code you used to create the objects. In the model, you are defining type relationships, not object relationships. So, a1 and a2 may point to the same object or different objects. The provided model definition defines a on

Norm 2.0.0

Sorry to bump the thread, but got a question for anyone who has used Norm. Can anyone tell me how to do a one to many relationship in Norm? The README says its possible, but I've run into some issues. Left an issue on the github repo, but figured I'd ask here as well. I've tried this approach: