Bug Report #999
Database only allows for single query space
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | % Done: | 0% |
||
| Category: | Libraries:Database | |||
| Target version: | 2.3.1 | |||
| Resolution: | fixed | Points: |
Description
Database only uses a single query space and thus is prone to clashing. Queries should ultimately be independent objects (object_db), but for now, this can be solved by using a stack for the query space.
History
Updated by John Heathco over 3 years ago
This is the first step into resolving #909 as well.
Updated by John Heathco over 3 years ago
- Status changed from New to Closed
- Resolution set to fixed
Updated by Woody Gilk over 3 years ago
- Status changed from Closed to Feedback
- Resolution deleted (
fixed)
Please list the revision number that closes this.
Updated by John Heathco over 3 years ago
- Status changed from Feedback to Closed
- Resolution set to fixed
Updated by John Heathco over 3 years ago
- Status changed from Closed to Feedback
- Resolution deleted (
fixed)
Updated by John Heathco over 3 years ago
Database's $query_history should be per-instance.
Updated by John Heathco over 3 years ago
- Status changed from Feedback to Closed
- Resolution set to fixed
Oops, it already is!