- Priority: Normal
- Number: 848
- Type: Feature
- Status: Assigned
- Age: 1516 Days
- Assignee: dykam
In an attempt to make queries clearer and easier to use, I've been thinking about a bunch of changes I want to apply:Structure queries
,is a multi-value seperator. E.g.:
:is a section separator. E.g.
"is the usual thing, allow spaces. E.g.
k:"a spaced keyword"
=is assignment. E.g.: `
- Predefined queries (with variables). Like mixin's.
chat: a:player-chat p:$0
- Filters. Basically purge queries with
Possibly transform it into some linked list or nested structure of sorts, where each node is a parameter. You can then easily transform, combine and verify them.
These are my ideas and I will try to get something workable in the next week.
This sounds like a great plan, it'll help make things more consistent and the stronger the abstraction/query building the easier it'll be to fix.
While you're working on these, try to keep in mind that I'll eventually be restructuring queries a little to fix:
- bug 836
- I've always been wanting to abstract out the query building to very easily allow for other syntax, like postgres, sqlite, etc
- Status → Accepted
Note I was mostly keeping just the QueryParameter object in mind, not the SQL query generation. However the abstractions I have in mind should make query generation easier. More notably, you would be able to add in custom parameters, and have the query generator warn the user that it was unable to process some parameter.
This would make it also easier to implement basic other-sql-query support, by not requiring full support right away.
Ok great. I just wanted to make sure you were aware of pending changes in that area.
- Assignee → dykam
- Status → Assigned
Creating a free account will let you immediately report issues on this project, as well as comment on existing issues, save your filters, and more!!