Unverified50% confidenceEventExact time
LectuLibre initially stored translations as JSON columns, and queries required constant JSON parsing, which was both painful and slow; after normalizing into a separate table, queries became cleaner and could directly leverage PostgreSQL's full-text search capabilities.
1
Sources
50%
Confidence
Long-term
Relevance
10/14/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedLectuLibre's FastAPI search endpoint completes websearch_to_tsquery parsing, @@ filtering, ts_headline highlighted snippet generation, and ts_rank relevance sorting in a single SQL query, avoiding the overhead of pulling the full text back to the application layer for processing.61% similarUnverifiedPostgreSQL's websearch_to_tsquery mimics Google search syntax, supporting double-quoted phrases, OR connections, and - exclusions, and it is highly tolerant of malformed input, making it more suitable for direct exposure to end users.59% similarUnverifiedEvidence使用「构建时数据获取」机制，在每次构建中执行SQL查询并将结果序列化为JSON文件嵌入静态页面57% similarUnverifiedAgentic Search tools like Tavily first understand the question, decompose it into sub-questions, select the best data source for each sub-question, then extract, perform vector retrieval, score and filter, and finally return structured JSON.55% similarUnverifiedPostgreSQL was chosen over plain text or vector databases because structured queries can precisely match fields such as error type and root-cause category without relying on fuzzy semantic-similarity search.54% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1023221API
curl https://kongchang.com/api/v1/knowledge/claims/1023221MCP
get_claim(id=1023221)