PEAR Bug Search Results

MDB2_Schema: Bug 21073 [Assigned] Cannot be installed using composer

lars at legestue dot net — 2016-06-03T11:44:52+00:00

MDB2_Schema Bug
Reported by lsolesen
2016-06-01T18:45:00+00:00
PHP: 5.6.22 OS: Ubuntu 1404 Package Version: 0.8.6

Description:
------------
It is impossible to install MDB2_Schema using composer. This is caused by 
the requirement on MDB2, which has a non-standard version number. Is it 
possible to have new releases of MDB2 which conforms to the standards 
used by composer?

MDB2_Schema: Bug 17849 [Open] Assigning an empty string to the default value

anterx at gmail dot com — 2010-09-07T14:52:27+00:00

MDB2_Schema Bug
Reported by anterx
2010-09-07T14:52:27+00:00
PHP: 5.2.8 OS: independed Package Version: 0.8.5

Description:
------------
The file MDB2/Driver/Reverse/mysqli.php contains this check


170    if (is_null($default) && $notnull) {
171        $default = '';
172    }


if type of filed is "date", for this field raises error:


888    return $this->raiseError(MDB2_SCHEMA_ERROR_VALIDATE,
889        '"'.$field_value.'" is not of type "'.$field_def['type'].'"');


what is wrong

MDB2_Schema: Feature/Change Request 16361 [Open] SPATIAL support.

derek at amplitude dot com dot au — 2009-06-22T08:00:42+00:00

MDB2_Schema Feature/Change Request
Reported by antigremlin
2009-06-22T08:00:42+00:00
PHP: Irrelevant OS: CentOS Package Version: 0.8.5

Description:
------------
Support for MYSQL's SPATIAL data formats (i.e: GEOMETRY, POINT, LINESTRING, POLYGON, MULTIPOINT, MULTILINESTRING, MULTIPOLYGON, GEOMETRYCOLLECTION)

MDB2_Schema: Feature/Change Request 16258 [Open] foreign key not supported in updateDatabase()

eslam dot bader at gmail dot com — 2009-05-24T22:11:42+00:00

MDB2_Schema Feature/Change Request
Reported by ebadr
2009-05-24T22:11:42+00:00
PHP: Irrelevant OS:  Package Version: 0.8.5

Description:
------------
when using updateDatabase() I realized that it don't support foreign key changes 

also the pre-requests for that like definition changes not supported

MDB2_Schema: Feature/Change Request 15886 [Open] Import Problem with Foreign Keys

g42 at gmx dot net — 2009-02-23T01:46:56+00:00

MDB2_Schema Feature/Change Request
Reported by tacki
2009-02-09T16:25:44+00:00
PHP: 5.2.8 OS: Fedora Package Version: 

Description:
------------
   I exported a simple mysql table-layout with 1 foreign key:




 test
 true
 false

 utf8

 table1

   
    id
    integer
    0
    true
    1
    true
    4
   

   
    fk
    integer
    0
    true
    true
    4
   

   
    fk
    
     fk
     ascending
    
   

   
    table1_ibfk_1
    SIMPLE
    NO ACTION
    NO ACTION
    fk
    
     

  

  
table2
     id
    
   

  

 

 table2

   
    id
    integer
    0
    true
    1
    true
    4
   

   
    data
    integer
    
    true
    4
   

  

  

  

 



Now i try to import it into a new table and receive an error. I added a sql-dump to show you the table in sql...

I think the problem is, that the fk is created before table2 even exists

Test script:
---------------
Script that i used to export the table:

$schema =& MDB2_Schema::factory($dsn);

$dump_options = array (
	'output_mode' => 'file',
	'output' => 'schema.xml',
	'end_of_line' => "\n"
);

$definition = $schema->getDefinitionFromDatabase();
$op = $schema->dumpDatabase($definition, $dump_options, MDB2_SCHEMA_DUMP_ALL);
var_dump($op);

Script to import:

$schema =& MDB2_Schema::factory($dsn);

$definition = $schema->parseDatabaseDefinitionFile('schema.xml');
$op = $schema->createDatabase($definition, array());
var_dump($op);

Expected result:
----------------
   true

Actual result:
--------------
   MDB2_Error

UserInfo: 
_doQuery: [Error message: Could not execute statement]
[Last executed query: ALTER TABLE table1 ADD CONSTRAINT table1_ibfk_1_idx FOREIGN KEY (fk) REFERENCES table2 (id) MATCH SIMPLE ON UPDATE NO ACTION ON DELETE NO ACTION]
[Native code: 1005]
[Native message: Can't create table './test/#sql-4714_1c8.frm' (errno: 150)]

MDB2_Schema: Bug 15276 [Open] Upgrading setting NOT NULL column default value to NULL

jan at horde dot org — 2009-08-25T12:00:56+00:00

MDB2_Schema Bug
Reported by yunosh
2008-12-09T14:58:00+00:00
PHP: Irrelevant OS:  Package Version: CVS

Description:
------------
If during a field update the default value is no longer set, the default value is set to NULL. When this happens, a check is missing whether this is allowed at all. The attached patch fixes this.
Alternatively this check might happen where the actual update query is build.

MDB2_Schema: Feature/Change Request 15064 [Verified] Improve PHPCS results?

daniel dot oconnor at gmail dot com — 2010-08-18T19:48:55+00:00

MDB2_Schema Feature/Change Request
Reported by doconnor
2008-11-18T06:47:08+00:00
PHP: 5.2.6 OS:  Package Version: CVS

Description:
------------
When I run PHPCS locally over it; I get:
A TOTAL OF 473 ERROR(S) AND 659 WARNING(S) WERE FOUND IN 12 FILE(S)

See also:
http://pear.cweiske.de/codingstandards/MDB2_Schema

Test script:
---------------
clockwerx@clockwerx-desktop:~/pear/MDB2_Schema/MDB2$ phpcs --report=summary .


Actual result:
--------------
clockwerx@clockwerx-desktop:~/pear/MDB2_Schema/MDB2$ phpcs --report=summary .

PHP CODE SNIFFER REPORT SUMMARY
--------------------------------------------------------------------------------
FILE                                                            ERRORS  WARNINGS
--------------------------------------------------------------------------------
...e/clockwerx/pear/MDB2_Schema/MDB2/Schema/Reserved/mssql.php  1       0
/home/clockwerx/pear/MDB2_Schema/MDB2/Schema/Reserved/oci8.php  1       0
...e/clockwerx/pear/MDB2_Schema/MDB2/Schema/Reserved/mysql.php  1       0
...e/clockwerx/pear/MDB2_Schema/MDB2/Schema/Reserved/ibase.php  1       0
...e/clockwerx/pear/MDB2_Schema/MDB2/Schema/Reserved/pgsql.php  1       0
/home/clockwerx/pear/MDB2_Schema/MDB2/Schema/Tool.php           10      9
...rx/pear/MDB2_Schema/MDB2/Schema/Tool/ParameterException.php  4       0
/home/clockwerx/pear/MDB2_Schema/MDB2/Schema/Parser2.php        42      49
/home/clockwerx/pear/MDB2_Schema/MDB2/Schema/Writer.php         54      143
/home/clockwerx/pear/MDB2_Schema/MDB2/Schema/Validate.php       71      48
/home/clockwerx/pear/MDB2_Schema/MDB2/Schema/Parser.php         12      139
/home/clockwerx/pear/MDB2_Schema/MDB2/Schema.php                275     271
--------------------------------------------------------------------------------
A TOTAL OF 473 ERROR(S) AND 659 WARNING(S) WERE FOUND IN 12 FILE(S)
--------------------------------------------------------------------------------

MDB2_Schema: Feature/Change Request 14985 [Open] Problems with atomic index updates

jan at horde dot org — 2008-11-15T18:52:50+00:00

MDB2_Schema Feature/Change Request
Reported by yunosh
2008-11-10T15:26:24+00:00
PHP: Irrelevant OS:  Package Version: 0.8.2

Description:
------------
Indexes are updated in one step when updating database schemas. This leads to problems because both, changing column definitions before, or after the indexes might not work.
One example: updating column widths might exceed the maximum index length of 1000 in MySQL, even though an index update would eliminate that index at a later step.
Thus, index updates should be split up, all changed/deleted indexes should be removed first, then the columns should be updated, then changed/added indexes should be added.

MDB2_Schema: Bug 14209 [Open] Default portability options not suitable for upgrading

holger dot schletz at web dot de — 2012-01-27T19:26:22+00:00

MDB2_Schema Bug
Reported by hschletz
2008-06-23T11:08:07+00:00
PHP: Irrelevant OS:  Package Version: 0.8.2

Description:
------------
I noticed some inconsistent behavior of updateDatabase() where the new schema had empty or missing  attributes. Depending on the previous state, the result was either a single space, an empty string or NULL (tested with PostgreSQL). Running a second pass of updateDatabase() with the same schema, some of the values changed again until they finally settled to a stable state.

This turned out to be a sideeffect of the MDB2_PORTABILITY_EMPTY_TO_NULL setting. Unsetting this flag gave the expected result (empty string for  or NULL when no default attribute was specified).

This portability option is really inadequate here. updateDatabase() should temporarily disable it. Although i have not tested this with Oracle (according to the MDB2 documentation Oracle's behavior is the reason for this option), this should work here too.

MDB2_Schema: Feature/Change Request 13779 [Assigned] Cannot pass createTable options on alterDatabaseTables

onokazu at gmail dot com — 2008-10-25T01:02:36+00:00

MDB2_Schema Feature/Change Request
Reported by onokazu
2008-04-26T18:04:53+00:00
PHP: 4.4.8 OS: OSX Package Version: 0.8.2

Description:
------------
When alterDatabaseTables() is called through updateDatabase(), there is 
not way to pass createTable() options such as type, charset. There 
should be an optional parameter in updateDatabase() method to pass in 
these option values.

MDB2_Schema: Feature/Change Request 13544 [Open] Default Timestamp Problems

g42 at gmx dot net — 2008-03-31T11:53:28+00:00

MDB2_Schema Feature/Change Request
Reported by tacki
2008-03-31T11:53:28+00:00
PHP: 5.2.5 OS: Fedora Core 8 Package Version: 0.8.2

Description:
------------
I don't know if this is a Problem of MDB2_Schema or MDB2 itself. 

I'd like to dump a Database from Postgre 8.2.7 to a XML and then import it into a MySQL5-Server. MDB2-version is 2.4.1.

I run into Problems while exporting Tables with Timestamp-values:

1. Problem - A Timestamp-Field must have a default Value. That's ok, i used '1970-01-01 00:00:00' for this field and exported the DB.

2. Problem - I tried to import (with updateDatabase()) and got this failure:
_doQuery: [Error message: Could not execute statement] [Last executed query: ALTER TABLE timers CHANGE id id VARCHAR(64) DEFAULT ' ' NOT NULL, CHANGE completiontime completiontime DATETIME DEFAULT '\'1970-01-01 00:00:00\'::timestamp without time zone' NOT NULL] [Native code: 1067] [Native message: Invalid default value for 'completiontime'] 
Looks like MySQL doesn't understand the Postgre-Timestamp Handling, or this Value is not correctly handled by the MDB2-Postgre-Driver.

So if i use a defaultvalue, i'll run into Problems during the Import, and if i won't use a defaultvalue, i'll run into Problems during Export.

I changed the Validate.php to allow empty-values (which are then set to default '1970-01-01 00:00:00' by MDB2_Schema), but if i set a non-empty value at Postgres, i'll still get an Error, because the MDB2_MySQL-Driver can't handle it.

Test script:
---------------
1. Postgre-Tabledata:
CREATE TABLE timers
(
  id character varying(64) NOT NULL,
  completiontime timestamp without time zone NOT NULL DEFAULT '1970-01-01 00:00:00'::timestamp without time zone,
  CONSTRAINT timers_pkey_idx PRIMARY KEY (id)
)

2. Dump it to a XML with getDefinitionFromDatabase() and dumpDatabase()

3. Import the XML to a MySQL-Database with updateDatabase()

Expected result:
----------------
No Error Message

Actual result:
--------------
_doQuery: [Error message: Could not execute statement] [Last executed query: ALTER TABLE timers CHANGE id id VARCHAR(64) DEFAULT ' ' NOT NULL, CHANGE completiontime completiontime DATETIME DEFAULT '\'1970-01-01 00:00:00\'::timestamp without time zone' NOT NULL] [Native code: 1067] [Native message: Invalid default value for 'completiontime']

MDB2_Schema: Feature/Change Request 12154 [Assigned] Multi-column primary key validation error

christoph at christophdorn dot com — 2008-10-25T01:22:43+00:00

MDB2_Schema Feature/Change Request
Reported by cadorn
2007-09-30T17:57:45+00:00
PHP: 5.2.1 OS: Mac OS X 10.4.10 Package Version: CVS

Description:
------------
I am trying to dump the schema of a wordpress database to an XML file as a test.

The dump fails with the following error:

there was already an primary index or autoincrement field in "wp_options" before "PRIMARY"

The schema of the wp_options table is as follows:

CREATE TABLE `wp_options` (
 `option_id` bigint(20) NOT NULL AUTO_INCREMENT,
 `blog_id` int(11) NOT NULL DEFAULT '0',
 `option_name` varchar(64) NOT NULL DEFAULT '',
 `option_can_override` enum('Y','N') NOT NULL DEFAULT 'Y',
 `option_type` int(11) NOT NULL DEFAULT '1',
 `option_value` longtext NOT NULL,
 `option_width` int(11) NOT NULL DEFAULT '20',
 `option_height` int(11) NOT NULL DEFAULT '8',
 `option_description` tinytext NOT NULL,
 `option_admin_level` int(11) NOT NULL DEFAULT '1',
 `autoload` enum('yes','no') NOT NULL DEFAULT 'yes',
 PRIMARY KEY (`option_id`,`blog_id`,`option_name`),
 KEY `option_name` (`option_name`)
) ENGINE=MyISAM AUTO_INCREMENT=119 DEFAULT CHARSET=utf8

Looks like the MDB2_Schema_Validator does not like the multi-column primary key? 

Test script:
---------------
require_once 'MDB2/Schema.php';

$dsn = 'mysql://root@localhost/WordPress';

$manager =& MDB2_Schema::factory($dsn, array('parser' => 'MDB2_Schema_Parser2'));
if (MDB2::isError($manager)) { die($manager->getUserinfo()); }
print 'Reverse Engineering Database';
$def = $manager->getDefinitionFromDatabase();
print_r($def);
print 'Dumping to XML';
$oldxml = $manager->dumpDatabase($def, array('output_mode' => 'file','output' => 'dump.xml'), MDB2_SCHEMA_DUMP_STRUCTURE);
var_dump($oldxml);


Expected result:
----------------
The validation should pass and the schema should be dumped to the dump.xml file.

Actual result:
--------------
[0] => Array
                (
                    [file] => /pinf/packages/pear.MDB2_Schema/MDB2/Schema.php
                    [line] => 2617
                    [function] => PEAR_Error
                    [class] => PEAR_Error
                    [type] => ->
                    [args] => Array
                        (
                            [0] => MDB2_Schema Error: schema validation error
                            [1] => -3
                            [2] => 1
                            [3] => 1024
                            [4] => there was already an primary index or autoincrement field in "wp_options" before "primary"
                        )

                )

MDB2_Schema: Feature/Change Request 11961 [Assigned] Custom Field Type

ifeghali at php dot net — 2007-09-03T13:30:14+00:00

MDB2_Schema Feature/Change Request
Reported by ifeghali
2007-09-02T03:30:49+00:00
PHP: Irrelevant OS:  Package Version: CVS

Description:
------------
I would love to have the ability to add annotations, so that if a database is created in a particular DBMS, you can specify exactly what kind of field to create. for instance, the kind of TEXT or INT field that is created.

In the  tag, you could have:


   BIGINT


this would allow advanced users to customize exactly how the field is created on different DBMS. beginners or people who don't care could use the guesswork, which is good enough for that level.

the reverse engineering script would just spit out the tags for the current DBMS and version. this would allow us to customize for mysql 4.0/4.1/5.0 and so on. the goal is not to support everything - it would only spit out what the current dbms is, and the user can customize it if needed for other dbms

* Feature requested by Greg *

MDB2_Schema: Bug 11696 [Open] getDefinitionFromDatabase() ends with ROLLBACK, without START TRANSACTION

floele at gmail dot com — 2008-03-10T20:40:39+00:00

MDB2_Schema Bug
Reported by floele
2007-07-28T13:19:18+00:00
PHP: Irrelevant OS: Irrelevant Package Version: CVS

Description:
------------
Hi once again ;)

I hope that I got an MDB2_Schema bug instead of an MDB2 one this time at least...

I recently submitted 11692 which already mentions my problem, but now I realised that this bug is in fact unrelated to it.

So what I am doing is thw following:

$db->supports('transactions') && $db->beginTransaction();
$db->query(...);

$previous_schema = $schema->getDefinitionFromDatabase();
die(); // usually I'd continue with updateDatabase() and a few more queries and then commit it all together, but that won't work either so I have this for simplicity.

Interestingly, the query log shows a ROLLBACK at the bottom, without a START TRANSACTION at the beginning.
See: http://pastebin.ca/637004
I highlighted the important parts.

Expected result:
----------------
Either no ROLLBACK at the end, or a new nested transaction at the beginning.

Actual result:
--------------
ROLLBACK at the end, without starting a new transaction.

MDB2_Schema: Feature/Change Request 10122 [Assigned] xinclude in schema files

tuxmaster at gmail dot com — 2007-02-26T17:06:00+00:00

MDB2_Schema Feature/Change Request
Reported by armen
2007-02-19T07:45:59+00:00
PHP: Irrelevant OS:  Package Version: 0.7.0

Description:
------------
It's better to give an example here. Let's say we have two initialization schema files. As MDB_Schema parser forces to have  in the  so we need to write declaration section in each file and it will cause duplication. This problem could be solved with an additional file containing the declaration section and including it in initialization files.
MDB2_Schema: Feature/Change Request 9452 [Open] Table charset, collation, engine options
pearbugs2006 at reddreamer dot com — 2007-06-10T23:44:14+00:00
MDB2_Schema Feature/Change Request
Reported by pearbugs2006@...
2006-11-25T07:47:48+00:00
PHP: 5.1.2 OS: Ubuntu 6.0 Package Version: 0.7.0

Description:
------------
I'm using MDB2_Schema with MySQL but as I'm creating an internationalized app I need to make sure I've got utf8 tables.  Right now MDB2_Schema just uses the defaults.  I simply rewrote Schema.php to always set utf8 when it creates a table, but it seems like this is an important feature to add.  In my case I wouldn't need to set each table individually, I'm using the same settings through the entire database.

MDB2_Schema: Feature/Change Request 8645 [Open] Add support for Views
joeboe at gmail dot com — 2006-09-07T13:35:55+00:00
MDB2_Schema Feature/Change Request
Reported by joeboe@...
2006-09-06T21:40:39+00:00
PHP: 5.1.6 OS: N/A Package Version: 0.6.0

Description:
------------
We would like to use MDB2_Schema to help manage changes on the dev db's when pushing to beta and live stages.  We use views in MySQL 5, which MDB2 seems to ignore.  It would be nice to see this added.

MDB2_Schema: Feature/Change Request 8075 [Open] FULLTEXT Support
michael at apison dot com — 2006-06-29T15:52:35+00:00
MDB2_Schema Feature/Change Request
Reported by michael@...
2006-06-29T15:52:35+00:00
PHP: 5.1.4 OS: irrelevant Package Version: 0.5.0

Description:
------------
It would be really cool if schema support fulltext indexes for MySQL (and equivalent for other RDBMSs)

Thanks!

Michael