Skip to content

Added documentation regarding DataCase and made clear that#2696

Open
Jsime34 wants to merge 2 commits into
ash-project:mainfrom
Jsime34:main
Open

Added documentation regarding DataCase and made clear that#2696
Jsime34 wants to merge 2 commits into
ash-project:mainfrom
Jsime34:main

Conversation

@Jsime34
Copy link
Copy Markdown

@Jsime34 Jsime34 commented May 12, 2026

not using it may generate DBConnection.OwnershipError Added a small test and explanation regarding this topic too at test-resources.livemd.
This was specifically made to tackle on Issue #2255.

Contributor checklist

Leave anything that you believe does not apply unchecked.

  • I accept the AI Policy, or AI was not used in the creation of this PR.
  • [] Bug fixes include regression tests
  • Chores
  • Documentation changes
  • Features include unit/acceptance tests
  • Refactoring
  • Update dependencies

not using it may generate `DBConnection.OwnershipError`
Added a small test and explanation regarding this topic
too at test-resources.livemd.
This was specifically made to tackle on Issue ash-project#2255.
%{total: 7, failures: 0, excluded: 0, skipped: 0}
```

## Testing AshPostgres
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm....I do worry about placing Postgres-specific docs here. Could we perhaps instead just say indicate that there are additional requirements when working with AshPostgres and link to the relevant docs in AshPostgres instead?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, the original issue asked for references to postgres, but i will follow your instructions. I will make another PR when ready.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah that makes sense, ultimately seeing it written out affected my thinking in terms of placement. Best to keep things colocated with their respective package as opposed to spreading out, difficult to manage otherwise. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants