-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JsonNamingPolicy Question #80
Comments
Hello Ronnie, The snake case policy follows the recommended practices for SurrealDB. Tables and fields uses snake case naming policy. |
I see. It caused me confusion because of the opposing convention to not
name c# properties that way. When I tried querying, my predicates weren’t
satisfied.
…On Sun, Feb 18, 2024 at 5:20 PM David Bottiau ***@***.***> wrote:
Hello Ronnie,
The snake case policy follows the recommended practices for SurrealDB.
Tables and fields uses snake case naming policy.
—
Reply to this email directly, view it on GitHub
<#80 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAYVJG2LRPY3MGKK5QPYGTYUJ5DTAVCNFSM6AAAAABDOO3AEGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJRGQ3DGMJQGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
@Odonno Where is that recommendation made and why? I don't see that practice in all of their examples. See this one for instance having fields like https://docs.surrealdb.com/docs/1.0.x/surrealql/statements/define/table/#schemaless-tables |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm curious what the reason is for choosing lowercase snake JsonNamingPolicy?
The text was updated successfully, but these errors were encountered: