Closed
Bug 774848
Opened 13 years ago
Closed 13 years ago
Remove version requirement on sqlalchemy <= 0.6.99
Categories
(Cloud Services Graveyard :: Server: Sync, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: gaston, Assigned: gaston)
Details
(Whiteboard: [qa+])
Attachments
(3 files)
|
994 bytes,
patch
|
rfkelly
:
review+
|
Details | Diff | Splinter Review |
|
1021 bytes,
patch
|
rfkelly
:
review+
|
Details | Diff | Splinter Review |
|
818 bytes,
patch
|
rfkelly
:
review+
|
Details | Diff | Splinter Review |
Followup to bug #654835, the requirement on sqlachemy <= 0.6.99 in -core, -reg and -storage doesnt seem to be needed anymore. I'm running sync server fine with sqlachemy 0.7.1, so i think the version requirement could be removed.
| Assignee | ||
Comment 1•13 years ago
|
||
Assignee: nobody → landry
Attachment #643129 -
Flags: review?(rfkelly)
| Assignee | ||
Comment 2•13 years ago
|
||
Attachment #643131 -
Flags: review?(rfkelly)
| Assignee | ||
Comment 3•13 years ago
|
||
Attachment #643132 -
Flags: review?(rfkelly)
Updated•13 years ago
|
Whiteboard: [qa?]
Comment 4•13 years ago
|
||
Thanks Landry. I can confirm that this works with sqlite for the basic functional tests, I'll have to take it for a spin on MySQL as well before committing. As another data point, what database are you using?
Updated•13 years ago
|
Attachment #643132 -
Flags: review?(rfkelly) → review+
Updated•13 years ago
|
Attachment #643129 -
Flags: review?(rfkelly) → review+
Updated•13 years ago
|
Attachment #643131 -
Flags: review?(rfkelly) → review+
Comment 5•13 years ago
|
||
Tests pass with mysql backend, including the custom code we have for doing DELETE with ORDER BY and LIMIT. So let's push ahead with this.
In addition to removing the version limit in setup.py, it will also need to be removed in the dev-reqs.txt file in each repo.
| Assignee | ||
Comment 6•13 years ago
|
||
(In reply to Ryan Kelly [:rfkelly] from comment #4)
> Thanks Landry. I can confirm that this works with sqlite for the basic
> functional tests, I'll have to take it for a spin on MySQL as well before
> committing. As another data point, what database are you using?
Plain default sqlite. I can do the commits/pushes if you want.
Comment 7•13 years ago
|
||
Committed in:
http://hg.mozilla.org/services/server-core/rev/3368df843ace
http://hg.mozilla.org/services/server-reg/rev/bc78d75507b0
http://hg.mozilla.org/services/server-storage/rev/6e866ec0079e
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 8•13 years ago
|
||
QA please verify this by checking that all tests pass with a fresh build of server-full. You'll need to build with CHANNEL=dev, and check that the version of sqlalchemy it built with is something in the 0.7 series. Do this to view the version:
./bin/pip freeze | grep SQLAlchemy
Also note that we haven't actually bumped the version of SQLAlchemy we're using in production. I've filed Bug 787278 to track that.
Whiteboard: [qa?] → [qa+]
Comment 9•13 years ago
|
||
So for a local install, I run the following from server-full:
$ ./bin/pip freeze | grep SQLAlchemy
SQLAlchemy==0.7.8
Verified.
Status: RESOLVED → VERIFIED
Updated•2 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•