Next | Query returned 35 messages, browsing 31 to 40 | previous

History of commit frequency

CVS Commit History:


   2007-10-25 18:59:59 by Johnny C. Lam | Files touched by this commit (980)
Log message:
Remove empty PLISTs from pkgsrc since revision 1.33 of plist/plist.mk
can handle packages having no PLIST files.
   2007-06-08 10:37:17 by Thomas Klausner | Files touched by this commit (2) | Package updated
Log message:
Update to 0.31:

0.31 Thu Mar 30 05:28:20 PST 2006
	- more schema update stuff:
	- added Column::sql_alter_column
	- added Table::sql_alter_table
	- added DBSchema::sql_update_schema and DBSchema::update_schema

0.30 Thu Feb 16 16:43:01 PST 2006
	- "Too much uptime"
	- Remove buggy debugging from Column.pm
	- Remove removed TODO from MANIFEST

0.29 Thu Feb 16 13:54:42 PST 2006
	- Column::sql_add_column fix when adding primary keys to Pg 7.2.x
	- workaround for PAUSE parsing of DBIx::DBSchema::DBD::Pg version: move
	  DBD::Pg verison checking after $VERSION declaration, thanks Andreas!
	- kludge: allow scalar ref default to force quoting off, to add things
	  like functions and empty values as defaults
	- Move TODO file to DBSchema.pm and DBS/Column.pm BUGS sections

0.28 Wed Nov 30 09:46:47 PST 2005
        - Initial SQLite support from Jesse Vincent
	- fix typo in DBIx::DBSchema::DBD POD doc
   2006-03-04 22:31:14 by Johnny C. Lam | Files touched by this commit (2257)
Log message:
Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no
developer is officially maintaining the package.

The rationale for changing this from "tech-pkg" to \ 
"pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list).  Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
   2005-11-24 19:45:43 by Thomas Klausner | Files touched by this commit (1)
Log message:
Fix DESCR, it really should say:

This module implements an OO-interface to database schemas.  Using
this module, you can create a database schema with an OO Perl
interface.  You can read the schema from an existing database.
You can save the schema to disk and restore it from different
process.  Most importantly, DBIx::DBSchema can write SQL CREATE
statements for different databases from a single source.

Currently supported databases are MySQL, PostgreSQL, Oracle and
Sybase.  DBIx::DBSchema will attempt to use generic SQL syntax for
other databases.  Assistance adding support for other databases is
welcomed.
   2005-11-24 19:44:16 by Thomas Klausner | Files touched by this commit (4) | Imported package
Log message:
Initial import of p5-DBIx-DBSchema:
This module helps abstract the process of working with complex
schemas of relational SQL database tables. As with DBI, it lets
you work with data a row at a time, but gives you the extra ability
to, with a single method call, reach across and grab rows of related
data from tables located elsewhere in your database, without having
to construct an SQL join clause yourself. The 'distance' from the
originating table to the related one can be arbitrarily long, so
long as they are related in some way -- i.e., could both return
data through a single (though perhaps quite lengthy) SQL query.


Next | Query returned 35 messages, browsing 31 to 40 | previous