[DBAL-1274] Travis only testing against PostgreSQL 9.4 Created: 30/Jul/15  Updated: 31/Jul/15

Status: Open
Project: Doctrine DBAL
Component/s: Platforms
Affects Version/s: 2.5.1
Fix Version/s: None
Security Level: All

Type: Bug Priority: Major
Reporter: Shane Archer Assignee: Benjamin Eberlei
Resolution: Unresolved Votes: 0
Labels: postgresql, travis


 Description   

There are two issues with the Travis configuration as it relates to testing against various versions of PostgreSQL.

The first is that the script inside .travis.yml is incorrectly single-quoting a conditional, causing it to appear to work but in fact do nothing. This line:

  - if [ '$DB' = 'pgsql' ]; then sudo service postgresql stop; sudo service postgresql start $POSTGRESQL_VERSION; fi

Should be changed to:

  - if [ $DB = 'pgsql' ]; then sudo service postgresql stop; sudo service postgresql start $POSTGRESQL_VERSION; fi

However, making that change raises the larger problem that since Travis is now running via containers, the "sudo" functionality is not possible, making the start/stop command unusable. It produces this:

$ if [ $DB = 'pgsql' ]; then sudo service postgresql stop; sudo service postgresql start $POSTGRESQL_VERSION; fi

sudo: must be setuid root
sudo: must be setuid root

The command "if [ $DB = 'pgsql' ]; then sudo service postgresql stop; sudo service postgresql start $POSTGRESQL_VERSION; fi" failed and exited with 1 during .

Your build has been stopped.

I am not sure if there is a long term strategy around this or not, but I couldn't find an open issue or PR related to it.



 Comments   
Comment by Shane Archer [ 31/Jul/15 ]

I tested this with the change mentioned in the description and the following:

sudo: required

That appeared to solve everything and produced a passing Travis build while actually appearing to load the proper PostgreSQL versions. Whether or not that is a good idea. I do think it would be nice to get Travis working again in this regard, though.





[DBAL-1273] [GH-888] Allow testing with doctrine/common 2.6 Created: 29/Jul/15  Updated: 29/Jul/15

Status: Open
Project: Doctrine DBAL
Component/s: None
Affects Version/s: None
Fix Version/s: None
Security Level: All

Type: Bug Priority: Major
Reporter: Doctrine Bot Assignee: Benjamin Eberlei
Resolution: Unresolved Votes: 0
Labels: None


 Description   

This issue is created automatically through a Github pull request on behalf of nicolas-grekas:

Url: https://github.com/doctrine/dbal/pull/888

Message:

By forbidding 2.6-dev, dbal 2.5 is untestable, because when composer tries to resolve deps to their highest, if has two choices:

  • doctrine/common@dev-master + dbal@2.4
  • or doctrine/common@2.5 + dbal@dev-master

and it chooses the first option.






[DBAL-1272] Invalid character for every request made with bindValue and execute Created: 28/Jul/15  Updated: 28/Jul/15

Status: Open
Project: Doctrine DBAL
Component/s: Drivers
Affects Version/s: None
Fix Version/s: None
Security Level: All

Type: Bug Priority: Major
Reporter: Xavier Coiffard Assignee: Benjamin Eberlei
Resolution: Unresolved Votes: 0
Labels: binding, driver, oracle
Environment:

Oracle, PHP 5.5



 Description   

I use Doctrine DBAL on a Silex project and try to insert some data into my Oracle database..

First i created the request in SQLDevelopper then i migrate it to my PHP code.

Here it is:
$sql = "INSERT INTO $table.FO_MAIN ( FOM_ID) VALUES (:id)";

$stmt = $app['db']->prepare($sql);
$stmt->bindValue('id', $data->id);
$stmt->execute();

My request is dead simple but the driver always crash on a ORA-00911: invalid character…I tried to remove/add semicolon, to switch from simple to double quote etc, but i get no luck on this...

It works great with executeQuery (without the bindValue).






[DBAL-1271] MySQL MEDIUMINT is mapped as type INT Created: 27/Jul/15  Updated: 27/Jul/15

Status: Open
Project: Doctrine DBAL
Component/s: Platforms
Affects Version/s: None
Fix Version/s: None
Security Level: All

Type: Bug Priority: Major
Reporter: Scott Connerly Assignee: Benjamin Eberlei
Resolution: Unresolved Votes: 0
Labels: None


 Description   

In MySqlPlatform in initializeDoctrineTypeMappings(), MEDIUMINT's are treated just the same as INT.

My particular use case is in the context of Laravel, renaming a column that is built as a MEDIUMINT. It gets rebuilt as an INT, and breaks the foreign keys.






Generated at Sun Aug 02 22:39:07 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.