DB Browser
This package provides a simple WSGI application to browse and edit database tables. The application was developed using the repoze.bfg web framework and uses the excellent JqueryUI library.
After installing and configuring the application, you will be able to browse and edit your application’s tables by visiting the configured URL path. All the configuration that is needed is an sqlalchemy database connection string for your database.
Installation
Install using setuptools, e.g. (within a virtualenv):
$ easy_install repoze.dbbrowser
Configuration inside another repoze.bfg application
This package includes a repoze.bfg view callable, so that from another repoze.bfg application, it is possible to configure it as a view. To do so, simply add a view declaration inside your configure.zcml. Note that your application’s settings must include the sqlalchemy database connection string for your database, under the name ‘db_string’:
<view
view="repoze.dbbrowser.dbbrowser.app_view"
name="dbbrowserapp"
/>
The result of the application call will be turned into a webob Response and returned to repoze.bfg as if the application was a view.
Alternatively, this can be accomplished via Python when adding a view to the repoze.bfg configurator:
from repoze.dbbrowser.dbbrowser import app_view config.add_view(app_view, name='dbbrowserapp')
Configuration via Paste
The application can also be ‘mounted’ into another WSGI application using Paste composite applications. Just choose a URL path for it and add the corresponding section:
[composite:main] use = egg:Paste#urlmap / = myapp /dbbrowser = dbbrowser [app:myapp] use = egg:myapp#app [app:dbbrowser] use = egg:repoze.dbbrowser#dbbrowser db_string = sqlite:///%(here)s/myapp.db theme_switcher = true default_theme = redmond
The only required parameter is ‘db_string’, which is an sqlalchemy database connection string.
The ‘theme_switcher’ parameter is a boolean indicating if JQuery UI theme switching functionality should be enabled.
The ‘default_theme’ parameter is a string giving the name of the JQuery UI theme to be used for the default dbbrowser UI. Keep in mind that JQuery stores this id in a cookie, so you may have to clear cookies for this setting to take effect if a previous theme was selected with the switcher.
Reporting Bugs / Development Versions
Visit http://bugs.repoze.org to report bugs. Visit http://svn.repoze.org to download development or tagged versions.
Changelog
0.1 (2010-03-02)
Initial release.
Metadata
Release files for repoze.dbbrowser 0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| repoze.dbbrowser-0.1.tar.gz | 306.0 kB | Without provenance | Details for repoze.dbbrowser-0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| repoze.dbbrowser-0.1-py2.6.egg | Legacy Egg format | - | - | Details for repoze.dbbrowser-0.1-py2.6.egg |
Total release size: 667.8 kB
Release files / repoze.dbbrowser-0.1.tar.gz
| Download URL | repoze.dbbrowser-0.1.tar.gz |
|---|---|
| Size | 306.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
718f2edef0a57091b7a77906d4cb746f1c45e9e790760fdbc6b3e97f81457da5
|
|
BLAKE2b-256 checksum How to use checksums |
4d6b645873a89e61a3379f1e44365b4d655d26c481a599d000b32710c6bf9a9b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / repoze.dbbrowser-0.1-py2.6.egg
| Download URL | repoze.dbbrowser-0.1-py2.6.egg |
|---|---|
| Size | 361.8 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
0799563bc296ea9a7f289b1de992c9f76a360a2614408cd60d06b33bfd39dc84
|
|
BLAKE2b-256 checksum How to use checksums |
243bd1c6e432414624dd76e588a825929d7b5392a5e1d194cdfc4c27cd1e4d52
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for repoze.dbbrowser 0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.