sails-disk does not support .transaction() method

[DominusKelvin]

Problem

The sails-disk adapter does not support the .transaction() method, which creates issues when developing applications that need transaction support.

Current Behavior

When attempting to use .transaction() with sails-disk:

await sails.getDatastore().transaction(async (db) => {
  // Transaction logic here
});

This fails because sails-disk lacks the .transaction() method implementation.

Expected Behavior

sails-disk should support the .transaction() method with pseudo transaction behavior, allowing the same transaction API to work consistently across development (sails-disk) and production (sails-postgresql, sails-mysql) environments.

Impact

• Cannot test transaction-dependent code during development with sails-disk
• Forces developers to use production adapters even for local development
• Creates development/production parity issues

Proposed Solution

Implement a pseudo transaction method in sails-disk that:

• Provides the same .transaction() API interface
• Uses in-memory state management for rollback capability
• Maintains transaction isolation within the adapter context

This would enable consistent development workflow while preserving sails-disk's lightweight nature.

[sailsbot]

@DominusKelvin Thanks for posting! We'll take a look as soon as possible.

In the mean time, there are a few ways you can help speed things along:

• look for a workaround. (Even if it's just temporary, sharing your solution can save someone else a lot of time and effort.)
• tell us why this issue is important to you and your team. What are you trying to accomplish? (Submissions with a little bit of human context tend to be easier to understand and faster to resolve.)
• make sure you've provided clear instructions on how to reproduce the bug from a clean install.
• double-check that you've provided all of the requested version and dependency information. (Some of this info might seem irrelevant at first, like which database adapter you're using, but we ask that you include it anyway. Oftentimes an issue is caused by a confluence of unexpected factors, and it can save everybody a ton of time to know all the details up front.)
• read the code of conduct.
• if appropriate, ask your business to sponsor your issue. (Open source is our passion, and our core maintainers volunteer many of their nights and weekends working on Sails. But you only get so many nights and weekends in life, and stuff gets done a lot faster when you can work on it during normal daylight hours.)
• let us know if you are using a 3rd party plugin; whether that's a database adapter, a non-standard view engine, or any other dependency maintained by someone other than our core team. (Besides the name of the 3rd party package, it helps to include the exact version you're using. If you're unsure, check out this list of all the core packages we maintain.)

---

Please remember: never post in a public forum if you believe you've found a genuine security vulnerability. Instead, disclose it responsibly.

For help with questions about Sails, click here.