#14435 closed (invalid)
postgis and NoSQL for postgre version 9.1 postgreQUEL
| Reported by: | Kristoffer Snabb | Owned by: | nobody |
|---|---|---|---|
| Component: | Uncategorized | Version: | dev |
| Severity: | Keywords: | NoSQL QUEL postgis | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
This is a feature request; all the following should work somehow:
Version 9.1 of postgre will be called postgreQUEL and will be a NoSQL database.
http://archives.postgresql.org/pgsql-hackers/2010-04/msg00003.php
The postgreQUEL is due to be released in 2011, and there should be postgreQUEL support in django?
And also how about the postGIS and their support for NoSQL, it can probably be done with multiple databases somehow, but is there
a recommended way of making postGIS geodjango, postgreQUEL etc. work with django.
Note:
See TracTickets
for help on using tickets.
I'm afraid you've been caught by an old April Fool's joke; QUEL is actually one of the languages Postgres originally implemented before they moved to SQL. The entire post is a joke, and it's posted on April 1st.
Closing as invalid.