| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
| |
When deleting a User, his/her collections can be deleted by
sqlalchemy: Collections do not need any special code to be
executed on deletion.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This feature is absolutely necessary. Now a user can simply define
their default license and quickly go through a form, as opposed to
stopping to click on the select and choosing the same option over
and over again.
Also added DB migration for the field, so that's working now, too.
Rebased by Sebastian and made the default value to be unicode.
Reviewed-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
|
|
|
|
|
|
|
| |
Merging an old branch, I reintroduced an import of db.sql.util rather than
db.util. Fixing the glitch.
Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
|
|
|
|
|
|
|
|
|
| |
Set User.collections to her Collections using the backref feature.
This way we can iterate a user's collections and delete them all.
Delete all MediaEntries/Files/attachments/comments/collections etc
before finally deleting the User object. This is the backend work for
issue 302 (allow a user to delete ones own account)
|
|
|
|
|
|
| |
Deleting a Collection should automatically delete all containing items.
Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Deleting a MediaEntry instance will automatically
delete all related comments and files/attachments. This moves
implementation logic out of views.py and allows to make use of this
functionality when e.g. deleting a User() account.
Whenever a MediaEntry entry is deleted, this will also sql-delete
the corresponding MediaFile entry.
Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
|
|
|
|
|
|
|
|
| |
This concludes the db.sql.* -> db.* move. Our db abstraction layer is
sqlalchemy, so there is no need to a separate db.sql.* hierarchy.
All tests have been run for each of the commit series to make sure
everything works at every step.
|
|
|
|
| |
No other functional changes.
|
| |
|
|
|
|
|
| |
To my surprise, there was only ONE reference to models.py.
From open.py.
|
|
|
|
| |
And change references.
|
|
|
|
|
| |
- Change some reference
- Provide a wrapper db/util.py
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
The .uploader() method conflicts with the uploader database
field. As we're moving to .FIELD for db field access, this
is a relevant conflict.
So renaming .uploader() to .get_uploader()
|
|
|
|
| |
will be ordered ascending, otherwise descending
|
|
|
|
|
|
|
|
|
| |
Note: Migrations can't use "Dot Notation"!
Migrations run on pymongo, not mongokit.
So they can't use the "Dot Notation".
This isn't really a big issue, as migrations are anyway
quite mongo specific.
|
|
|
|
|
|
|
|
|
|
| |
mongokit documents can allow to use x.FIELD instead of
x["FIELD"].
First it looks a lot more pythonic.
Second it might allow us an easier migration path towards
an sqlalchemy database backend.
Docs: http://namlook.github.com/mongokit/tutorial.html#dot-notation
|
|\
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
mediagoblin/db/migrations.py
mediagoblin/db/models.py
mediagoblin/user_pages/views.py
mediagoblin/util.py
|
| |
| |
| |
| |
| |
| |
| | |
* Removed trailing whitespace
* Line length < 80 where possible
* Honor conventions on number of blank lines
* Honor conventions about spaces around :, =
|
| | |
|
|/
|
|
| |
tools/[file].py
|
|\
| |
| |
| |
| | |
Conflicts:
mediagoblin/auth/routing.py
|
| | |
|
| | |
|
|/ |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Conflicts:
mediagoblin/db/migrations.py
|
| |
| |
| |
| |
| | |
- deleted the thumbnail_file from the media_entries collection
- added a migration to remove the field from previous db versions
|
|\| |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
mediagoblin/config_spec.ini
mediagoblin/edit/views.py
mediagoblin/util.py
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- adds a function to convert the tag list of dicts to a text string
properly delimited for loading into forms
- tag string conversion function updated to generate list of dicts
- updates all mentions of the conversion of the string to the tags db
object
- adds a tags template utility and updates the media template accordingly
|
|/ / |
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
mediagoblin/db/migrations.py
mediagoblin/db/models.py
mediagoblin/process_media/__init__.py
mediagoblin/templates/mediagoblin/user_pages/media.html
mediagoblin/util.py
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* `migrations.py`
* Removed empty line
* Added empty line
* `models.py`
* Added `MediaEntry.get_display_media()` helper function
* `process_media.__init__.py`
* Updated `process_media_initial()`
* Renamed `main` => `original`.
* Added condition to `medium`, it's only created if the original
dimensions exceed the MEDIUM_SIZE dimensions.
* `media.html`
* The image tag is now populated by `MediaEntry.get_display_media()`
* `util.py`
* Added `DISPLAY_IMAGE_FETCHING_ORDER`, used by `MediaEntry.get_display_media()`
|
|\ \ \ |
|
| | |/
| |/| |
|
|/ / |
|
| |
| |
| |
| | |
the merge!
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
'remotes/gullydwarf-cfdv/f423_match_image_ordering_between_scroll_and_gallery'
Conflicts:
mediagoblin/db/models.py
|
| | | |
|