mapper. Its primary goal is to provide an object-oriented layer with
what we consider to be the key aspects of OO, i.e. polymorphism and
message dispatch, without hindering the power of an RDBMS. It is
designed to "feel pythonic", without encouraging the typical ORM
behavior such as potato programming.
Axiom provides a full interface to the database, which strongly
suggests that you do not write any SQL of your own. Metaprogramming is
difficult and dangerous (as many, many SQL injection attacks amply
demonstrate). Writing your own SQL is still possible, however, and
Axiom does have several methods which return fragments of generated
schema if you wish to use them in your own queries.
ok martynas@
binary suid root.
This caused lots of problems with the calendar and other stuff because the
evolution-data-server didn't run correctly.
Well, evolution-data-server is currently broken because of the libsoup
major update. It needs an update to a more recent version.
pgFouine is a PostgreSQL log analyzer used to generate detailed reports
from a PostgreSQL log file. pgFouine can help you to determine which
queries you should optimize to speed up your PostgreSQL based
application.
from Pierre-Emmanuel Andre <pea at raveland dot org>
pgloader imports data from a flat file and insert it into a database
table. It uses a flat file per database table, and you can configure as
many Sections as you want, each one associating a table name and a data
file.
[...]
from Pierre-Emmanuel Andre <pea at raveland dot org>
you apply this and restore afterwards!
Additionally, implicit typecasts are history and not supported anymore.
Versions prior to 8.3 had the feature (some say bug) that functions,
expecting an argument to be of a certain type, have casted a variable of
any other type to the expected type, if possible.
This has changed now. Tests surfaced rare occurrences of regressions,
which were then fixed in about ten minutes - and that code was not even
in the ports tree; no issues found there.
A few more things have changed, namely tsearch2 went from contrib to the
core and native uuid type support was added; for details read the
release announcement at
http://www.postgresql.org/docs/8.3/static/release-8-3.html.
tests & ok mbalmer@ (maintainer)
After discussions with a few people and testing of how upgrades will
be handled, mark this FLAVOR as broken so existing -bdb users don't
break their installation with pkg_add -u. Those wishing to upgrade
must dump their database, remove the openldap-*-bdb package, then
they are free to install the new unFLAVORed version and restore
the database.
This can be revisited after release, hopefully OpenLDAP 2.4 (which
requires newer DB) will be stable by then.
ok mbalmer (MAINTAINER)
add a pkg/MESSAGE-server teaching the user how to launch slapd in rc.local as
_openldap user.
english 'looks fine' jmc@, and ok ajacoutot@ mbalmer@ (maintainer)
- Adds textproc/p5-XML-SAX-Writer as a RUN_DEPENDS
- Removes the pkgspec from the RUN_DEPENDS because all of the required
versions are lower than the oldest version in the tree
ok simon@, steven@
Manager version H3 (2.1.2).
This is a bugfix release that also fixes privilege escalation in the Horde API
and missing ownership validation in the share management. All users are
encouraged to upgrade to this version.
The major changes compared to the Mnemo H3 (2.1.1) version are:
* Fixed privilege escalation in the Horde API.
* Fixed missing ownership validation on share changes.
* Updated Finnish, Japanese, Portuguese, Simplified Chinese, Spanish, and
Traditional Chinese translations.
* Small bug fixes and improvements.
The full list of changes (from version H3 (2.1.1)) can be viewed here:
http://cvs.horde.org/diff.php/mnemo/docs/CHANGES?r1=1.63.2.37&r2=1.63.2.38.2.3&ty=h
Storm is a fast object-relational mapper (ORM) for Python and used in
Canonical's Launchpad project. Storm is developed in a test-driven
manner, provides small and clean public APIs and works with everything
from SQLite to PostgreSQL and MySQL.
From Will Maier
ok kili@, eric@
DBIx::DataModel is a wrapper framework for building Perl abstractions
(classes, objects and datastructures) that interact with relational
database management systems (RDBMS). Of course the ubiquitous DBI
module is used as a basic layer for communicating with databases; on
top of that, DBIx::DataModel provides facilities for generating SQL
queries, joining tables automatically, navigating through the results,
converting values, and building complex datastructures so that other
modules can conveniently exploit the data.
ok sthen@
Testing with databases can be tricky. If you are developing a system
married to a single database then you can make some assumptions about
your environment and ask the user to provide relevant connection
information. But if you need to test a framework that uses DBI,
particularly a framework that uses different types of persistence
schemes, then it may be more useful to simply verify what the framework
is trying to do -- ensure the right SQL is generated and that the
correct parameters are bound.
DBD::Mock makes it easy to just modify your configuration (presumably
held outside your code) and just use it instead of DBD::Foo (like
DBD::Pg or DBD::mysql) in your framework.
ok sthen@
- enable linking against already installed libdb.so instead of the
internally shipped static library
"no objections here" martynas@
mostly done somewhere between budapest and amsterdam
