#69 closed enhancement (fixed)
Enhancing the MySQL backend
| Reported by: | Owned by: | Adrian Holovaty | |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
I've implemented the dictfetch*() functions. May not be extremely fast, but at least the functionality is there. I'm not sure about the edge cases, though; we probably want the mysql and postgres backends to do the same thing when, for example, fetchmany() is called going over the result set bounds. Document this in the docstrings?
Attachments (1)
Change History (2)
by , 19 years ago
| Attachment: | my-dict.diff added |
|---|
comment:1 by , 19 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Fixed in [190]. Thanks, Manuzhai! I used your basic idea but made some performance tweaks.
Note:
See TracTickets
for help on using tickets.
Fix the dictfetch*() function for the MySQL backend.