-
Notifications
You must be signed in to change notification settings - Fork 228
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
Full text search documentation page #442
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
doc/mapping/full-text-search.md
Outdated
@@ -2,9 +2,149 @@ | |||
|
|||
PostgreSQL has [built-in support for full-text search](https://www.postgresql.org/docs/current/static/textsearch.html), which allows you to conveniently and efficiently query natural language documents. | |||
|
|||
*TO BE COMPLETED* | |||
## Mapping | |||
PostgreSQL full text search types are mapped onto C# types built-in to Npgsql. The ```tsvector``` type is mapped to ```NpgsqlTsVector``` and ```tsquery``` is mapped to ```NpgsqlTsQuery```. This means you can use properties of type ```NpgsqlTsVector``` directly in your model to create ```tsvector``` columns. The ```NpgsqlTsQuery``` type on the other hand, is used in LINQ queries. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe .NET types?
FYI, you can use single backticks to make inline code blocks (:
f818672
to
595794e
Compare
@YohDeadfall Wording updated, backticks adjusted. |
Just a comment on the identifier quoting: Per the release notes:
So this: WHERE "c"."SearchVector" @@ 'Npgsql' could be simplified to: WHERE c."SearchVector" @@ 'Npgsql' |
595794e
to
bf42507
Compare
@YohDeadfall No longer quoting "c". |
@austindrenski @rwasef1830 Thanks! I think it can be merged now. |
@roji Here's the documentation page for full text search. Let me know what you think. This is a follow up to #1.