databases using mysqldump.
Features:
- Backup mutiple databases
- Single backup file or to a seperate file for each DB
- Compress backup files
- Backup remote servers
- E-mail logs
WWW: https://sourceforge.net/projects/autobackupmysql
PR: ports/141846
Submitted by: Frank Wall <fw at moov.de>
- Use USERS and GROUPS functionality, instead of supplying pkg-install
- Drop some warnings about changes that happened a long time ago now.
PR: 141802
Submitted by: Matthew Seaman <m.seaman@infracaninophile.co.uk> (maintainer)
- Use USERS and GROUPS functionality , instead of supplying pkg-install
- Drop some warnings about changes that happened a long time ago now.
PR: 141801
Submitted by: Matthew Seaman <m.seaman@infracaninophile.co.uk> (maintainer)
e-mail addresses from the pkg-descr file that could reasonably
be mistaken for maintainer contact information in order to avoid
confusion on the part of users looking for support. As a pleasant
side effect this also avoids confusion and/or frustration for people
who are no longer maintaining those ports.
PR/137956 by Ashish SHUKLA (thanks!). [1]
Those ports which define EMACS_PORT_NAME to be "emacs21" were
not touched (this time). They may be converted to the new
world order by removing the above mentioned assignment.
Four ports were marked as BROKEN with EMACS_PORT_NAME=emacs23
(they do not compile):
. lang/bigloo;
. mail/wanderlust;
. mail/wanderlust-devel;
. www/emacs-w3m.
Three ports were marked as IGNORE with EMACS_PORT_NAME=emacs23:
. japanese/egg-canna (the port version is dated as of 2001,
does not compile with Emacs 23 and seems it cannot be fixed);
. deskutils/remember.el (was incorporated into Emacs 23);
. editors/nxml (was incorporated into Emacs 23).
Changes that were made after (and as a result of) exp run. For
those ports:
. japanese/migemo-emacs21;
. japanese/migemo-emacs22
EMACS_PORT_NAME?= was changed to EMACS_PORT_NAME= to the apropriate
emacs port name.
PR: ports/137956 [1], ports/141369 [2]
Submitted by: Ashish SHUKLA <wahjava at gmail.com> [1],
bsam (me) [2]
Exp-run by: miwi
All code, at first, is written in pure Python so that py-postgresql will work
anywhere that you can install Python 3. Optimizations in C are made where
needed, but are always optional.
Prepared Statements
Using the PG-API interface, protocol-level prepared statements may be created
and used multiple times. db.prepare(sql)(*args)
COPY Support
Use the convenient COPY interface to directly copy data from one connection to
another. No intermediate files or tricks are necessary.
Arrays and Composite Typescw
Arrays and composites are fully supported. Queries requesting them will returns
objects that provide access to the elements within.
"pg_python" Quick Console
Get a Python console with a connection to PostgreSQL for quick tests and simple
scripts.
WWW: http://python.projects.postgresql.org/
PR: ports/137782
Submitted by: Volodymyr Kostyrko <c.kworr@gmail.com>
another database (with same schema) at any time. Use as a constant
dataset for running tests against or for populating development
databases when impractical to use production clones. Describe fixture
set using relations and conditions based on your DBIx::Class schema.
WWW: http://search.cpan.org/dist/DBIx-Class-Fixtures/
