MongoEngine / MongoEngine/mongoengine
unable to access gridfs in a different database
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.3k
- Forks
- 1.2k
- Avg merge
- 4h 41m
- Merged PRs (30d)
- 11
Description
I've been accessing my other database just fine using db_alias for most collections that do not contain FileField() or ImageField() fields. However, for collections with FileField() or ImageField() I have not been able to access the file in the other database. Does db_alias not properly link fs.files and fs.chunks in the other database? Must one somehow add meta = {"db_alias": "OtherDB"} to fs.files and fs.chunks?
class File(db.Document):
file = db.ImageField()
meta = {"db_alias": "OtherDB"}
for i in File.objects.all():
print i.file # Shows '<ImageGridFsProxy: (no file)>'
print i.file.length # Shows 'AttributeError'
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the File model with db_alias set to OtherDB and inspect how FileField/ImageField access GridFS through fs.files and fs.chunks. Check the ImageGridFsProxy path, and consider the issue resolved when file access and length work from the aliased database.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mongodb, python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100