Project status? about mammoth HOT 5 CLOSED

OK, I just updated the repo. Let me know what you think.

As for the changes: some bugs are fixed and a lot of typing improvements e.g. when inserting specifying id is not required anymore. :) On delete and update cascade/restrict/no action/set null/set default and a handful more sql keywords are supported now.

from mammoth.

I moved this project to a submodule of a project of mine (which is in production), but continued development, so a lot of changes are not pushed to this repo yet. I'll take some time to this week to move back to this public repo and publish to npm.

The philosophy of the public api is to stick as close as possible to PostgreSQL—to avoid any unnecessary abstractions. So, the api is fairly stable, as in it won't suddenly change, but there are still some sql commands not supported.

I'll keep this issue open until I updated the repo again. But feel free to ask any questions in the meantime.

from mammoth.

I'm also highly interested in this library. What kind of changes have you made?

from mammoth.

@martijndeh Any update on project status? I would love to use mammoth in my new project.

from mammoth.

I'm not working on a project which uses postgres and typescript right now, so new development is paused currently. I think it needs some dependency updates and check with the latest typescript again. Still, I think Mammoth is feature-complete enough to be usable, especially because I value the type safety so much. But yea officially the status is still pre-production.

from mammoth.