Projects tagged ‘database’, ‘django’, and ‘python’

South is a database migration framework for Django applications.

Project is an Operation Support System (OSS) for the Telco, Serice provider and Enterprize Network Operation Centers (NOC). Areas covered by NOC: Fault Management Service Activation/Provisioning ... [More] Multi-VRF Address space management Configuration Management DNS provisioning Peering management, RPSL and BGP filters generator, integrated looking glass Reporting NOC Project is Open Source Software distributed under the term of BSD-like LICENSE. [Less]

The pgmigrate tool is developed for managing changes in database structure between a project members. It does so by managing so called 'patches'. Small pieces of SQL or Python code which modifies ... [More] database schema. So far it supports only PostgreSQL. Starting from 1.2.0 can be easily integrated with Django to solve schema migration issue. [Less]

django-firebirdThis is a firebird backend implementation for django that enables Firebird (version 1.5 and later) RDBMS support. Currently it works only with Django 1.1 (trunk revision) This module ... [More] is based on version of Hajime Nakagami, which I (maxirobaina) have improved to work with django 1.1 and Firebird 1.5 and Firebird 2.x This is alpha software - use it at your own risk. InstallationPrerequisites KInterbasDB package (http://www.firebirdsql.org/index.php?op=devel&sub=python) Get django 1.1 (http://www.djangoproject.com/download/) Go ahead... Download the zip file, extract it and copy under django/db/backends/ folder on your django installation or... Check out the latest development version anonymously with: $ svn checkout http://django-firebird.googlecode.com/svn/trunk/ django-firebird-read-only Differences from other Django backends TextField. Since large and very large VARCHARs work better than BLOBs with Firebird in most cases where Django uses TextField, Firebird backend uses VARCHAR columns for TextFields and BLOB columns for LargeTextField. For more info see http://www.volny.cz/iprenosil/interbase/ip_ib_strings.htm#_strings_blob_varchar. With Firebird backend TextFields have max_length and encoding attributes that are ignored by other backends. By default, TextFields have max_length of 10921 (with default UNICODE_FSS 3-byte charset), 8191 (with optional 4-byte UTF8 charset) or 32765 (with custom 1-byte encoding) -- maximum allowed. If there are multiple TextFields, their size could be adjusted to fit the 64k row limit and warning will be genererated. It's better to set explicit max_length attribute in this situation. If you need to store more text you could use LargeTextField or split your text across multiple rows. Index Limit. 252 bytes with Firebird < 2.0 and 1/4 of page size in later versions. You may need to add encoding="ascii" and/or adjust max_length of CharFields used as indexes or unique/primary keys to work around these Firebird limitations. Current implementation adjusts these fields automagically and generates warnings during validation process. It's better to adjust these fields manually or switch to Firebird > 2.0 and/or increase the page size. Foreign Key Constraints. FK constraint in Firebird are stricter - no forward references allowed, even inside transactions. UsageIn setting.py DATABASE_ENGINE = 'firebird' DATABASE_NAME = 'path_to_database' # Path to database or db alias DATABASE_USER = 'SYSDBA' # Your db user DATABASE_PASSWORD = 'masterkey' # db user password DATABASE_HOST = '127.0.0.1' # Your host machine DATABASE_PORT = '3050' # If is empty, use default 3050 DATABASE_OPTIONS = {'charset':'ISO8859_1'} #If is not defined, use default UNICODE_FSS [Less]

Django External Schema Evolution Branch Django, via the command ./manage syncdb, can automatically build a database schema based on your applications models.py file. However, after you've done this ... [More] once, it leaves you with two unpleasant follow-up options if you ever make any changes to your model structure: 1. destroy your existing schema (along with all your data) and let ./manage syncdb rebuild it for you 2. manage your own schema upgrades by writing your own SQL Project deseb aims to fill this void by providing s third option: 3. generate schema upgrades via the command: ./manage evolvedb [Less]

This is a command line tool written in Python. It displays all the differences between two database schemas. The schema are provided as SQL dump. 1. ExampleInputdb1.sql: sql dump of a database with ... [More] a single table: 'person' CREATE TABLE `person` ( `last name` varchar(50) NOT NULL, `date_of_birth` varchar(45) NOT NULL, PRIMARY KEY (`last name`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8;db2.sql: sql dump of the same database after adding a new table 'car' and modified fields in the 'person' table. CREATE TABLE `car` ( `color` varchar(50) NOT NULL, `number_plate` varchar(50) NOT NULL, `brand` varchar(50) NOT NULL, PRIMARY KEY (`number_plate`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8; CREATE TABLE `person` ( `last name` varchar(50) NOT NULL, `date_of_birth` datetime NOT NULL, `first_name` varchar(45) NOT NULL, PRIMARY KEY (`last name`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8;Commandpython compdb.py db1.sql db2.sqlOutput% FIELD: person.date_of_birth `date_of_birth` varchar(45) NOT NULL => `date_of_birth` datetime NOT NULL + FIELD: person.`first_name` varchar(45) NOT NULL + TABLE: car 3 difference(s).2. Notation%: difference +: new field or table -: missing field or table 3. LimitationsCurrently works only with MySQL dumps Obviously this tool cannot detect when the name of a field or a table has changed! 4. MotivationThis script was originally written to help me keep track of the evolution of Django models (hence the Python implementation). Before upgrading a staging server, I would compare the SQL dump from my development database (generated with mysqldump -d or with python manage.py sql) with the dump from my staging server. Note that more sophisticated tools have been developed for this purpose, search for 'django schema evolution' on any search engine to find them. This tool was developed as part of a UML to Django conversion project. 5. FeedbackYour comments and contributions are welcome. [Less]

Import, store and retrieve news from the web. - use provided websites importers or build your own very easily - newsmemory will parse the web and store the articles periodically - a web interface ... [More] lets you browse the news or search the database - flag a newsitem, the others users will see it as flagged [Less]

This project started by my necessity to replicate & aggregate from many Oracle databases to one MySQL database. I was provided only with read-only access to the Oracle servers & databases. So far ... [More] django_replicate can do Master-Slave replication in the following manner: one-to-one table, many-to-one (fan-in) and one-to-many (fan-out) incremental replication. Differential replication with deletes & updates and full snapshot support is in the works. Django_replicate can be added as a Django app to an existing project or as a stand alone program. All configuration for django_replicate is done through the django admin interface. Logging is done using the python logging facility so sending the logs to diferent destination is easy, by default logs are sent to the console and to an internal t [Less]

Django Treebeard django-treebeard is a library that implements efficient tree implementations for the Django Web Framework 1.0+. It includes 3 different tree implementations: Adjacency List ... [More] , Materialized Path and Nested Sets. Each one has it’s own strength and weaknesses (see Benchmarks) but share the same API, so it’s easy to switch between implementations. django-treebeard uses Django Model Inheritance with abstract classes to let you define your own models. To use django-treebeard: 1. Download a release from the treebeard download page or get a development version from the treebeard subversion repository. 2. Run python setup.py install 3. Add 'treebeard' to the INSTALLED_APPS section in your django settings file. 4. Create a new model that inherits from one of django-tree [Less]

NamedQuerySets are the foundation for quickly defining, building, and publishing the contents of a Django QuerySet. You start with a plain QuerySet, give it a name, and define some public filters. ... [More] After some basic templating, you've got a newegg-style content browser. The filter state is a small string, so that after drilling down in the content browser, the same filter can be bookmarked, turned into an RSS feed, a website widget, or email alerts (like Google Alert) without much extra effort. NamedQuerySets also support browsing/filtering of multiple querysets on the same page, automatically maintaining each NQS's filter state independently within the URL querystring. The code works, but the API isn't finalized yet. A handful or two of issues are under active development, before we declare 1.0. For a demo of NamedQuerySets in action, visit http://www.chinabizevents.com/ [Less]