Document wildcard schema support - #557
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
| The wildcard character can only be used as the last character in the table name. To match tables across multiple schemas instead, see [Wildcard Schemas](/sync/advanced/schemas-and-connections#wildcard-schemas-postgres). | ||
|
|
||
| When using wildcard table names, the original table suffix is available in the special `_table_suffix` column. This works the same way in both Sync Streams and Sync Rules: | ||
| When using wildcard table names, you can filter on the original table suffix. In Sync Streams with `edition: 3`, use the `table_suffix()` function, prefixed with the table name or alias from the `FROM` clause (requires PowerSync Service v1.24.0 or later). In legacy Sync Rules, the suffix is available as the special `_table_suffix` column instead: |
There was a problem hiding this comment.
In Sync Streams with
edition: 3,
We should not mention non-edition: 3 Sync Streams at all, let's just say Sync Streams.
There was a problem hiding this comment.
I'm not sure if I understand your comment correctly, I think what you're saying is that we shouldn't point out edition 3 specifically because A, edition 2 was just the alpha so not really a case we need to continue documenting and B: this will become false as soon as we release edition 4?
There was a problem hiding this comment.
A, edition 2 was just the alpha so not really a case we need to continue documenting
This exactly, I did not consider (B) in my comment.
2 participants
Resolves #540
🤖 Drafted by Claude Code after passing it the original PR and this issue as context. Reviewed (mostly for stylistic/readability concerns) and polished by me.
Should still get a review for technical accuracy.