Doctrine Project

[DBAL-479] Doctrine2 schema-tool:update doesn't re-create foreign keys on entity change

Duplicate — Mon, 1 Apr 2013 16:47:29 +0000

I have changed a @ManyToOne relation to another entity. My workflow was this:

Having @ManyToOne(targetEntity="Entity\EntityA") in the source
Creating the database schema
Changing @ManyToOne(targetEntity="Entity\EntityA") to @ManyToOne(targetEntity="Entity\EntityB")
Calling doctrine orm:schema-tool:update

orm:schema-tool:update doesn't notice that and doesn't re-create the FK on MySQL and PostgreSQL (haven't tested others).

[DBAL-220] Some platforms require specific index handling

Tue, 29 Jan 2013 03:06:08 +0000

SQL Server/Azure for example requires strict differentiation between CLUSTERED/NON-CLUSTERED indexes.
MySQL can create full text indexes
etcetc.

[DBAL-161] Character Set of Database not UTF-8

Tue, 20 Nov 2012 06:33:33 +0000

Hi Guys,

I was working with symfony command line and created the database with the app/console doctrine:create:database

Though the characterset I specified was UTF-8 , it created Latin character set .

@elliot was right too, the create database is not using any character set https://github.com/doctrine/dbal/blob/master/lib/Doctrine/DBAL/Platforms/MySqlPlatform.php#L328

You can see the issue created at https://github.com/symfony/symfony/issues/2044 and later Fabien confirmed the bug is related to Doctrine .

I am not sure its a Bug or a feature I am asking .

Thanks

[DBAL-342] [GH-198] Change default MySQL table collation to utf8_unicode_ci

Mon, 12 Nov 2012 17:00:13 +0000

This issue is created automatically through a Github pull request on behalf of VladanStef:

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

Message:

I think default table collation should be changed to `utf8_unicode_ci`, as it handles properly a much wider array of characters (Cyrillic, for example) at a generally negligible cost of performance.

`utf8_general_ci` simply does not work properly with too many languages and should be avoided as a default.

[DBAL-335] Is MasterSlaveConnection implemented correctly - seems to overwrite master connection on transaction methods?

Sat, 22 Sep 2012 23:46:31 +0000

Forgive me to doubt, but I think there may be a bug in MasterSlaveConnection.

It's easier to understand what I'm saying by debugging and tracing the flow, but I'll illustrate it with gists.

First, here is a simple service method to create a user. It opens up a transaction, persists the user, commits and returns. On error, if there is an active transaction, rollback. Here is the gist:

https://gist.github.com/3547674

The "$conn->beginTransaction();" line is where we trace through (the remainder of the service method is now irrelevant). Looking into MasterSlaveConnection.php, we see the method tries to connect to the master connection (call this point ###):

https://gist.github.com/3547720

Now looking in the next gist, we see what happens when "$this->connect('master');" is called. At this point it's not that interesting, the internal "$this->_conn" property is set to "master".

https://gist.github.com/3547750

Now here lies the bug I believe. "parent::beginTransaction();" is called. When looking into this method, we see that another call is made to connect but this time without "master" as the argument (i.e. connect to slave). This call to connect is made before incrementing the transaction nesting level.

https://gist.github.com/3547808

Now, I won't do another gist for "MasterSlaveConnection::connect", but if you refer to the file at line 13 https://gist.github.com/3547750#file_master_slave_connection.php, you will see that it checks the transaction nesting level and if it is there, forces master. However, we don't increment the level until after the method returns, so the slave is used. Ultimately, this results in the internal "$this->_conn" property set to the "slave" connection which violates our original action at ### above where we said we want to connect to "master".

Am I missing something here? Here is a gist the is a basic attempt at fixing this one method. It simply copies the code from the parent method except does not connect twice. I believe the same would have to occur for all the other methods unless it can be fixed once at the "MasterSlaveConnection::connect" level.

https://gist.github.com/3547880

I've just fleshed out "beginTransaction", "commit" and "rollBack" in "MasterSlaveConnection" by basically copying and pasting the code from the parent class and for my failing use case, this fixes the issue. However, it did require updating "Connection" slightly so that I had access to some private variables.

[DBAL-191] GH-85: [WIP] Drizzle Support

Sat, 22 Sep 2012 14:35:03 +0000

Pull-Request was automatically synchronized: https://github.com/doctrine/dbal/pull/85

Drizzle platform support
Driver is using pdo_mysql

All DBAL tests complete except PortabilityTest.

[DBAL-346] Generated schema fails on MySQL (BLOB/TEXT cant have DEFAULT value)

Thu, 20 Sep 2012 17:29:30 +0000

In my symfony 2.1 project i was including JMSPaymentCoreBundle and did the vanilla installation.

After that i ran

php app/console doctrine:schema:update --dump-sql
php app/console doctrine:schema:update --force

A lot of schema updates were done. I ran it again, and two schema updates were still showing up.
Running the command again, and they still show up.

I then tried to run the two schema updates against my database and MySQL complains with the following error:

Error: 1101 - BLOB/TEXT column 'extended_data' can't have a default value

According to the Documentation BLOB/TEXT indeed cannot have default values. I am not sure why Doctrine thinks it has to set this default value.

The statements look like this:

sascha@debian:/var/www/myproject/Symfony$ php app/console doctrine:schema:update --dump-sql
ALTER TABLE payment_instructions CHANGE extended_data extended_data LONGTEXT NOT NULL COMMENT '(DC2Type:extended_payment_data)';
ALTER TABLE financial_transactions CHANGE extended_data extended_data LONGTEXT DEFAULT NULL COMMENT '(DC2Type:extended_payment_data)'

I already reported this problem in the JMSPaymentCoreBundle Issue Queue where i then was referred to over here.

Also, i am not sure if Doctrine DBAL is the best match for this issue, so if it is wrong please move it to the right project issue queue.

Thank you very much and best of Regards!
Sascha

[DBAL-341] [GH-197] Bugfix for DDC-2013

Mon, 17 Sep 2012 10:26:33 +0000

This issue is created automatically through a Github pull request on behalf of naitsirch:

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

Message:

Bugfix DDC-2013 - Default Session Value ".," for "NLS_NUMERIC_CHARACTERS". This is needed because Oracle uses other characters for decimal separation depending on the servers locale.

See http://www.doctrine-project.org/jira/browse/DDC-2013

[DBAL-345] When inserting decimals into Oracle, getting ORA-01722: invalid number

Mon, 17 Sep 2012 10:23:27 +0000

When I insert decimals into database I get the following error message:

ORA-01722: invalid number

Oracle wants decimals (e.g. NUMBER(5,2)) separated by comma instead of a dot. I think the reason is that I use the german version of Windows. I tried to modify the following method of \Doctrine\DBAL\Driver\OCI8\OCI8Statement::bindValue() just for testing of course:

    public function bindValue($param, $value, $type = null)
    {
        if (is_float($value)) {
            $value = str_replace('.', ',', (string) $value); // <--
        }
        return $this->bindParam($param, $value, $type);
    }

With this modification I do not get the error anymore.
It would be great if a solution could be found. The strange thing is, if I query "SELECT * from nls_database_parameters where PARAMETER='NLS_NUMERIC_CHARACTERS'" I get ".," which means that a dot is already used as decimal separator. Maybe Oracle preferes the Locale of the OS?!
Maybe you could provide a setting which defines what separator should be used for decimals.

I found some Links that might be interesting regarding this issue:

[DBAL-334] [GH-194] Small test fixes for PostgreSQL

Wed, 5 Sep 2012 17:25:22 +0000

This issue is created automatically through a Github pull request on behalf of posulliv:

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

Message:

When running the test suite against a clean PostgreSQL install on a 64-bit system I hit 2 issues:

dropDatabase calls fail unless a database is manually created
TypeConversionTest::testIdempotentDataConversion fails expecting bigint type to be converted to a string. PostgreSQL seems to detect 32 vs 64 bit systems and casts correctly for bigint types.

This small patch allows the test suite to run successfully for me against clean MySQL & PostgreSQL installs.

[DBAL-339] setFetchMode arguments exception

Wed, 5 Sep 2012 16:52:37 +0000

i have this error in version 2.3.0-RC1

in DBAL/STatement.php on aound line 191 you will find:

public function setFetchMode($fetchMode, $arg2 = null, $arg3 = null)

{ return $this->stmt->setFetchMode($fetchMode, $arg2, $arg3); }

the problem is that php throws me a Exception:
Fatal error: Uncaught exception 'PDOException' with message 'SQLSTATE[HY000]: General error: fetch mode doesn't allow any extra arguments'

the reason for the exception is that setFetchMode doesnt support null as second/third argument.

somebody also described it in the php issue tracker:
https://bugs.php.net/bug.php?id=54545

[DBAL-338] Typo in AbstractPlatform for GUID type declaration

Wed, 5 Sep 2012 16:44:44 +0000

has been fixed in 3f5fda98299acdcda9965e8e797cbcd0490f0dcc, however it's not merged into 2.3.

[DBAL-329] [GH-190] Fix DDC-1978

Wed, 29 Aug 2012 09:36:59 +0000

This issue is created automatically through a Github pull request on behalf of FabioBatSilva:

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

Message:

Fix ~~DDC-1978~~

http://www.doctrine-project.org/jira/browse/DDC-1978

[DBAL-314] [GH-180] Fixed some phpdoc

Tue, 14 Aug 2012 21:48:41 +0000

This issue is created automatically through a Github pull request on behalf of stof:

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

Message:

This fixes some phpdoc in the AbstractPlatform and in some child classes. I haven't checked all child classes to ensure that all phpdoc is right now, but the abstract one is now accurate (but a bunch of method are missing their phpdoc altogether)

[DBAL-315] [GH-182] Added a missing method in the Constraint interface

Tue, 14 Aug 2012 21:33:08 +0000

This issue is created automatically through a Github pull request on behalf of stof:

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

Message:

This adds a missing method in the Constraint interface. The method is already defined in AbstractAsset which is extended by both classes implementing the interface. the AbstractPlatform is calling this method on objects after checking they are implementing the interface. So either the method should be part of the interface, or all places using the interface as typehint should be refactored to check for the classes (examples can be found [here](https://github.com/doctrine/dbal/blob/master/lib/Doctrine/DBAL/Platforms/AbstractPlatform.php#L1029) and [there](https://github.com/doctrine/dbal/blob/master/lib/Doctrine/DBAL/Platforms/AbstractPlatform.php#L1254)).

Adding a method in an interface is technically a BC break but this method is not really a public extension point. what do you think @beberlei ?

[DBAL-322] Change Detection fails when 'unsigned' is used in MySQL Schema

Tue, 14 Aug 2012 21:10:15 +0000

Change Detection fails when 'unsigned' is used in MySQL Schema

[DBAL-298] [GH-166] Fixes a bug caused by unquoted reserved table name being referenced during schema creation

Sun, 29 Jul 2012 08:13:48 +0000

This issue is created automatically through a Github pull request on behalf of klaussilveira:

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

Message:

When creating a schema with tables with reserved names and relationships between them, the schema creation tool failed to write valid SQL in MySQL due to unquoted table names. For example:

CREATE TABLE `Group` (id INT AUTO_INCREMENT NOT NULL, name VARCHAR(255) NOT NULL DEFAULT NULL, PRIMARY KEY(id)) ENGINE = InnoDB;
CREATE TABLE User (id INT AUTO_INCREMENT NOT NULL, username VARCHAR(255) NOT NULL PRIMARY KEY(id)) ENGINE = InnoDB;
CREATE TABLE UserHasGroup (user_id INT NOT NULL, group_id INT NOT NULL, INDEX IDX_617A865CA76ED395 (user_id), INDEX IDX_617A865CFE54D947 (group_id), PRIMARY KEY(user_id, group_id)) ENGINE = InnoDB;
ALTER TABLE UserHasGroup ADD CONSTRAINT FK_617A865CA76ED395 FOREIGN KEY (user_id) REFERENCES User (id);
ALTER TABLE UserHasGroup ADD CONSTRAINT FK_617A865CFE54D947 FOREIGN KEY (group_id) REFERENCES Group (id);

This fix creates a small function for creating quoted foreign key table names.

[DBAL-301] [GH-167] Oracle stored procedures

Sun, 29 Jul 2012 07:53:12 +0000

This issue is created automatically through a Github pull request on behalf of AduroIdea:

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

Message:

driver function
To avoid ORA-03131 error, data length must be passed to oci_bind_by_name function.
This commit fixes it so now pdo_oci can be used with stored procedures and output parameters from sql/plsql.

[DBAL-302] [GH-168] DebugStack should ignore stopQuery when disabled

Tue, 10 Jul 2012 07:32:26 +0000

This issue is created automatically through a Github pull request on behalf of dpb587:

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

Message:

I noticed that DebugStack was adding an empty element when it was disabled. This PR changes it to match startQuery with its behavior.

1) Doctrine\Tests\DBAL\Logging\DebugStackTest::testLoggedQueryDisabled
Failed asserting that two arrays are equal.
— Expected
+++ Actual
@@ @@
Array
(
+ [0] => Array
+ (
+ [executionMS] => 1341871660.9651
+ )
+
)

I've submitted the PR to 2.0.x since that's where the bug is first seen and is still listed as stable on doctrine-project.org. Preferably this could also be applied to newer branches as well, or I can also submit separate PRs.

[DBAL-243] setCharset raises an error when using pdo_sqlite

Thu, 5 Jul 2012 21:02:37 +0000

When I attempt to use setCharset("utf8") with pdo_sqlite, this fails.

I know that pdo_sqlite doesn't support SET NAMES utf8, however, this should be caught by the driver (like: throwing a NotSupportedException) or simply ignore setCharset (mainly because if you allow the user to choose their backend, developers don't need to introduce special cases for driver handling).

[DBAL-296] [GH-165] interface compatibility

Thu, 5 Jul 2012 19:37:15 +0000

This issue is created automatically through a Github pull request on behalf of Nazin:

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

Message:

[DBAL-295] [GH-164] Getters for AbstractAsset$_quoted and ForeignKeyConstraint$_options

Thu, 5 Jul 2012 19:08:46 +0000

This issue is created automatically through a Github pull request on behalf of tyler-sommer:

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

Message:

Added the necessary getters, re: doctrine/migrations#79

[DBAL-178] Unknown column type requested

Tue, 26 Jun 2012 21:06:00 +0000

When I run doctrine:schema:create, doctrine throw the following exception:
[Doctrine\DBAL\DBALException]
Unknown column type requested.

( Note: their is 2 spaces between type and requested )

The problem with this error message is how much it's unspecific. Event with -v, I still have no clue about that type is wrong, and what file is concerned.
So basically, I have to manually look at all my mapping files, one by one.

Also note that doctrine:mapping:info return all OK.

[DBAL-271] [GH-143] added simple_array type

Sun, 27 May 2012 15:49:57 +0000

This issue is created automatically through a Github pull request on behalf of schmittjoh:

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

Message:

[DBAL-288] [GH-156] [Platform] Allow a string to be passed as type

Sun, 27 May 2012 15:49:34 +0000

This issue is created automatically through a Github pull request on behalf of schmittjoh:

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

Message:

[DBAL-287] [GH-155] Update license for Composer

Sun, 27 May 2012 08:07:24 +0000

This issue is created automatically through a Github pull request on behalf of jalliot:

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

Message:

[DBAL-279] [GH-147] 2.2 Add lastInsertId() support for OCI8 Driver

Tue, 22 May 2012 19:21:29 +0000

This issue is created automatically through a Github pull request on behalf of franek:

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

Message:

Add lastInsertId() support for Sequence

[DBAL-278] add support for lastInsertId method on OCI8 Driver

Tue, 22 May 2012 19:21:16 +0000

The method lastInsertId() is not defined for OCI8 Driver in Doctrine\DBAL\Driver\OCI8\OCI8Connection.php :

OCI8Connection.php

public function lastInsertId($name = null)
{
    //TODO: throw exception or support sequences?
}

I propose this method to handle lastInsertId for sequence :

OCI8Connection.php

public function lastInsertId($name = null)
 {
        // For sequence
        if (is_string($name)) {
            // We can check eventually check the presence of the sequence in the table
            // USER_SEQUENCES
            $sql = 'SELECT ' . $name . '.CURRVAL FROM DUAL';
            // will throw an exception if this sequence does not exist
            $stmt = $this->query($sql);
            $result = $stmt->fetch(\PDO::FETCH_ASSOC);
            if ($result !== false && isset($result['CURRVAL'])) {
                return (int) $result['CURRVAL'];
            }
    }
    // OCI8 driver does not provide support of lastInsertId
    return null;
}

Thanks,

[DBAL-270] [GH-142] Dbal 264

Tue, 22 May 2012 17:56:01 +0000

This issue is created automatically through a Github pull request on behalf of rivaros:

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

Message:

added support for Postgres UUID type.

[DBAL-281] [GH-149] changed some phpdoc's, set correct namespaces and types

Tue, 22 May 2012 17:53:09 +0000

This issue is created automatically through a Github pull request on behalf of Engerim:

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

Message:

[DBAL-280] [GH-148] No bug. Respect the case used in the interface

Tue, 22 May 2012 17:47:40 +0000

This issue is created automatically through a Github pull request on behalf of pap-florin:

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

Message:

[DBAL-283] [GH-151] Fixed the doctrine/common constraint and added the branch-alias

Tue, 22 May 2012 17:13:37 +0000

This issue is created automatically through a Github pull request on behalf of stof:

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

Message:

The change in the requirements requires doctrine/common#144 to be merged and parsed by Packagist, otherwise ``2.3.*`` would not match anything.

[DBAL-282] [GH-150] Added missing regex delimiters in the testsuite

Tue, 22 May 2012 17:12:47 +0000

This issue is created automatically through a Github pull request on behalf of stof:

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

Message:

The AbstractSchemaManager expects getting the regex with its
delimiters since 8beb732fe9 but the tests were not updated.

[DBAL-272] [GH-144] [MYSQLI] Fixed infinite loop in fetchAll()

Wed, 9 May 2012 07:00:08 +0000

This issue is created automatically through a Github pull request on behalf of kimhemsoe:

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

Message:

[DBAL-238] Disable MultipleActiveResultSets in SQL Server (pdo_sqlsrv) not possible

Sat, 5 May 2012 11:46:40 +0000

http://msdn.microsoft.com/en-us/library/ee376925%28v=sql.90%29.aspx

[DBAL-259] [GH-134] Removed Paranthesis to allow for more complex Regex

Sat, 5 May 2012 11:40:38 +0000

This issue is created automatically through a Github pull request on behalf of Hounddog:

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

Message:

Needed to remove the Paranthesis to allow for complex Regular Expressions. e.g Exclusion of tables

[DBAL-214] Unable to use PDO::FETCH_CLASS with a call to fetch()

Sat, 5 May 2012 08:52:55 +0000

EDITED: 2nd attempt to describe this - first one was confusing.

I don't understand why the setFetchMode() method of Doctrine\DBAL\Driver\PDOStatement drops any arguments passed to it. It means that PDO::FETCH_CLASS cannot be used with calls to fetch() and no warning is given until the point when the underlying \PDOStatement complains that no class has been specified.

[DBAL-262] [GH-136] Support oci8 in TableGenerator

Sat, 5 May 2012 07:45:25 +0000

This issue is created automatically through a Github pull request on behalf of dpb587:

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

Message:

Bug fix: yes
Feature addition: no
Backwards compatibility break: no
[![Build Status](https://secure.travis-ci.org/dpb587/dbal.png?branch=bugfix-TableGenerator)](http://travis-ci.org/dpb587/dbal)

This test was breaking when running under `oci8` due to Oracle's deference to upper case column names. I realize Oracle has built-in sequences and `TableGenerator` is unnecessary, in theory, but it seemed like the class should work if possible. I see pgsql is in the same boat.

Tested with:

phpunit -c oci8.phpunit.xml.dist tests/Doctrine/Tests/DBAL/Functional/TableGeneratorTest.php

Before:

PHPUnit 3.5.13 by Sebastian Bergmann.

Time: 0 seconds, Memory: 10.25Mb

There were 2 errors:

1) Doctrine\Tests\DBAL\Functional\TableGeneratorTest::testNextVal
Exception: [Doctrine\DBAL\DBALException] Error occured while generating ID with TableGenerator, aborted generation: Undefined index: sequence_value

2) Doctrine\Tests\DBAL\Functional\TableGeneratorTest::testNextValNotAffectedByOuterTransactions
Exception: [Doctrine\DBAL\DBALException] Error occured while generating ID with TableGenerator, aborted generation: Undefined index: sequence_value

After:

PHPUnit 3.5.13 by Sebastian Bergmann.

Time: 1 second, Memory: 10.25Mb

OK (2 tests, 5 assertions)

[DBAL-246] [GH-125] PHPDoc blocks improvments + 1 CS Fix

Fri, 4 May 2012 18:05:02 +0000

This issue is created automatically through a Github pull request on behalf of adrienbrault:

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

Message:

Hey guys,

I started to fix a class type inside Connection and then i went ahead to see what i could also improve!

Adrien

[DBAL-248] [GH-127] Fix Statement class passing bound objects to SQL logger

Fri, 4 May 2012 18:04:31 +0000

This issue is created automatically through a Github pull request on behalf of jimcottrell:

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

Message:

This commit saves converted parameter values in bindValue() so the later call to the SQL logger in execute() will not pass bound objects without type information.

[DBAL-250] [GH-128] [DBAL-249] result cache with fetch type PDO::FETCH_COLUMN

Fri, 4 May 2012 18:04:13 +0000

This issue is created automatically through a Github pull request on behalf of gedrox:

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

Message:

This should enable caching of results retrieved by PDO::FETCH_COLUMN fetch type.
Before this exception "Invalid fetch-style given for caching result" was raised.

Should work now.

(This replaces a previous pull request #126 I failed to make right... sorry)

[DBAL-266] [GH-139] [Mysql Platform] Added mapping for binary and varbinary.

Fri, 4 May 2012 17:47:36 +0000

This issue is created automatically through a Github pull request on behalf of kimhemsoe:

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

Message:

[DBAL-252] [GH-131] [mysqli] Added mysqli driver to travis tests.

Mon, 16 Apr 2012 17:02:02 +0000

This issue is created automatically through a Github pull request on behalf of kimhemsoe:

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

Message:

[DBAL-251] [GH-130] [mysqli] Added support for fetchAll(PDO::fetch_column)

Mon, 16 Apr 2012 17:01:56 +0000

This issue is created automatically through a Github pull request on behalf of kimhemsoe:

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

Message:

[DBAL-166] Table Encoding on generation table creation query

Sun, 1 Apr 2012 11:42:46 +0000

Can not set charset options for table creation.
Now I am fix thix problem in patch.
File: doctrine-dbal/lib/Doctrine/DBAL/Schema/Schema.php

#!/usr/bin/php
<?php
/**

Doctrine DBAL Patch
fix table creation query encode
(c) _Nicolay
*/
system ('cp ./vendor/doctrine-dbal/lib/Doctrine/DBAL/Schema/Schema.php ./vendor/doctrine-dbal/lib/Doctrine/DBAL/Schema/Schema.php.Orig');

$data = file_get_contents('./vendor/doctrine-dbal/lib/Doctrine/DBAL/Schema/Schema.php');
$data = str_replace("new Table(\$tableName);",
"new Table(\$tableName,array(),array(),array(),0,array('charset'=>'utf8','collate'=>'utf8_general_ci'));",
$data);
file_put_contents('./vendor/doctrine-dbal/lib/Doctrine/DBAL/Schema/Schema.php', $data);

[DBAL-229] oic8 oci_pconnect is not surported

Sat, 31 Mar 2012 09:26:38 +0000

public function __construct($username, $password, $db, $charset = null, $sessionMode = OCI_DEFAULT)
{
if (!defined('OCI_NO_AUTO_COMMIT'))

{ define('OCI_NO_AUTO_COMMIT', 0); }

$this->_dbh = @oci_connect($username, $password, $db, $charset, $sessionMode);
if (!$this->_dbh)

{ throw OCI8Exception::fromErrorInfo(oci_error()); }

}

How can i use oci_pconnect in oic8 driver?

[DBAL-208] Uniqueidentifier MSSQL type is not supported in DBAL

Sat, 24 Mar 2012 09:07:43 +0000

My Symfony2 projects currently use main trunks of the Doctrine projects, the latest release merge into this branch was 2.2.0-BETA2, that's why I mentioned it in"Affected versions". Sorry if mistaken.

I would like to report that MSSQL Driver/Platform still does not support the 'uniquidentifier' field type of MSSQL.

Trying to introspect the database with
php app/console doctrine:mapping:import MMPTestDBBundle annotation
we get the error

[Doctrine\DBAL\DBALException]
  Unknown database type uniqueidentifier requested, Doctrine\DBAL\Platforms\SQLServer2008Platform may not support it.

There is a related issue, opened and fixed in Doctrine1 project
http://www.doctrine-project.org/jira/browse/DC-253

Going to fix this issue in the same way. Any help greatly appreciated.

[DBAL-241] Add fetchAll(PDO::FETCH_COLUMN) support to OCI8 driver

Sat, 24 Mar 2012 09:05:21 +0000

See https://github.com/doctrine/dbal/pull/52

[DBAL-224] Allow drop index and pk from table instance

Mon, 13 Feb 2012 16:10:26 +0000

Allow drop index and pk from table instance

[DBAL-223] Add DBAL TableGenerator

Dependency — Mon, 13 Feb 2012 14:11:35 +0000

/**
 * Table ID Generator for those poor languages that are missing sequences.
 *
 * WARNING: The Table Id Generator clones a second independent database
 * connection to work correctly. This means using the generator requests that
 * generate IDs will have two open database connections. This is necessary to
 * be safe from transaction failures in the main connection. Make sure to only
 * ever use one TableGenerator otherwise you end up with many connections.
 *
 * TableID Generator does not work with SQLite.
 *
 * The TableGenerator does not take care of creating the SQL Table itself. You
 * should look at the `TableGeneratorSchemaVisitor` to do this for you.
 * Otherwise the schema for a table looks like:
 *
 * CREATE sequences (
 *   sequence_name VARCHAR(255) NOT NULL,
 *   sequence_value INT NOT NULL DEFAULT '1',
 *   sequence_increment_by INT NOT NULL DEFAULT '1',
 *   PRIMARY KEY (table_name)
 * );
 *
 * Technically this generator works as follows:
 *
 * 1. Use a robust transaction serialization level.
 * 2. Open transaction
 * 3. Acquire a read lock on the table row (SELECT .. FOR UPDATE)
 * 4. Increment current value by one and write back to database
 * 5. Commit transaction
 *
 * If you are using a sequence_increment_by value that is larger than one the
 * ID Generator will keep incrementing values until it hits the incrementation
 * gap before issuing another query.
 *
 * If no row is present for a given sequence a new one will be created with the
 * default values 'value' = 1 and 'increment_by' = 1
 *
 * @author Benjamin Eberlei <kontakt@beberlei.de>
 */

[DBAL-222] Add Azure Platform

Mon, 13 Feb 2012 11:47:35 +0000

SQL Azure has some platform specific SQL on top of SQL Server 2008 mainly to support Federations

[DBAL-216] Add ext/sqlsrv support

Mon, 13 Feb 2012 11:21:40 +0000

Currently we only have support for PDO_SQLSRV, however some of the Azure/Advanced functionality strictly needs the sqlsrv extension.