[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#264051: marked as done (ITP: php-mdb -- a database abstraction layer)

Your message dated Wed, 24 May 2006 11:59:29 -0600
with message-id <E1Fixdp-0004Yz-Lt@merkel.debian.org>
and subject line WNPP bug closing
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: wnpp
Severity: wishlist

* Package name    : php-mdb
  Version         : 1.3.0
  Upstream Author : Lukas Kahwe Smith <smith@php.net>
* URL             : http://pear.php.net/package/MDB
* License         : BSD style
  Description     : a database abstraction layer


 PEAR MDB is a merge of the PEAR DB and Metabase php database abstraction
 layers.   It provides a common API for all support RDBMS.
 The main difference to most other DB abstraction packages is that MDB goes much
 further to ensure portability.
 .
 Among other things MDB features:
 .
   * An OO-style query API
   * A DSN (data source name) or array format for specifying database
     servers
   * Datatype abstraction and on demand datatype conversion
   * Portable error codes
   * Sequential and non sequential row fetching as well as bulk fetching
   * Ordered array and associative array for the fetched rows
   * Prepare/execute (bind) emulation
   * Sequence emulation
   * Replace emulation
   * Limited Subselect emulation
   * Row limit support
   * Transactions support
   * Large Object support
   * Index/Unique support
   * Module Framework to load advanced functionality on demand
   * Table information interface
   * RDBMS management methods (creating, dropping, altering)
   * RDBMS independent xml based schema definition management
   * Altering of a DB from a changed xml schema
   * Reverse engineering of xml schemas from an existing DB
     (currently only MySQL)
   * Full integration into the PEAR Framework
   * Wrappers for the PEAR DB and Metabase APIs
   * PHPDoc API documentation
 .
 Currently supported RDBMS:
 .
   * MySQL
   * PostGreSQL
   * Oracle
   * Frontbase
   * Querysim
   * Interbase/Firebird
   * MSSQL


-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (995, 'unstable'), (990, 'experimental'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.7-ck5
Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro (ignored: LC_ALL set to fr_FR@euro)

--- End Message ---
--- Begin Message --- 
Hello,

This is an automatic mail sent to close the ITP you have reported or 
are involved with.

Your ITP wnpp bug is being closed because of the following reasons:
- It is, as of today, older than 365 days.
- It hasn't had any activity recently.

As this is an automatic procedure, it could of course have something
wrong and probably it would be closing some bugs that are not 
intended by owners and submitters (like you) to be closed, for
example if the ITP is still of your interest, or there has been 
some kind of activity around it. In that case, please reopen the
bug, do it, DO IT NOW! (I don't want to be blamed because of
mass closing and not let people know that they can easily reopen
their bugs ;-).

To re-open it, you simply have to mail control@bugs.debian.org
with a body text like this:

reopen 264051
thanks bts

Further comments on the work done in the bug sent to
264051@bugs.debian.org would be truly welcomed.
Anyway, if you have any kind of problems when dealing with
the BTS, feel free to contact me and I'd be more than happy to help
you on this: <damog@debian.org>.

A similar process is being applied to other kind of wnpp bugs.

Thanks for your cooperation,

 -- David Moreno Garza <damog@debian.org>.

--- End Message ---
Reply to: