PEAR Bug Search Results

MDB2_Driver_pgsql: Feature/Change Request 21047 [Open] Datatype ($db_type) interval missing

kontakt at itloesungen dot com — 2016-03-31T19:08:51+00:00

MDB2_Driver_pgsql Feature/Change Request
Reported by jugantner
2016-03-31T19:08:51+00:00
PHP: Irrelevant OS: independant Package Version: 1.5.0b4

Description:
------------
In file MDB2/Driver/Datatype/pgsql.php in function _mapNativeDatatype (row 411ff) the type "interval" is missing. Its a timestamp-timestamp datatype in postgres.

It would be nice to include this datatype to the next release.

Are there any release plans?
If no, how can I help?

Expected result:
----------------
datatype ($db_type) "interval" can be processed

Actual result:
--------------
datatype "interval" is unknown and thus a resultset cannot be analysed with the Reverse module if a column has datatype "interval".

MDB2_Driver_pgsql: Bug 19974 [Open] Bug in named placeholder parameter substitution in prepare()

gacek at intertele dot pl — 2013-06-11T15:50:04+00:00

MDB2_Driver_pgsql Bug
Reported by gacek
2013-06-11T15:50:04+00:00
PHP: Irrelevant OS:  Package Version: 1.5.0b4

Description:
------------
When using named placeholders (with option emulate_prepared==false),
prepare() function misplaces them due to wrong $parameter counter usage.




Test script:
---------------
Try such SQL statement (transcription):

$result=query_row('SELECT CAST(:p1 AS TEXT) AS r1, CAST(:p2 AS TEXT) AS r2, CAST(:p1 AS TEXT) AS r3, CAST(:p3 AS TEXT) AS r4',
  array(                                                                                                      
    'p1'=>'v1',
    'p2'=>'v2',
    'p3'=>'v3'
  )
)                 




Expected result:
----------------
array(
  'r1'=>'v1',
  'r2'=>'v2',
  'r3'=>'v1',
  'r4'=>'v3'
)

Actual result:
--------------
From postgresql.log: 
EXECUTE db2_statement_pgsql_2878e7cd3a2411850038698262023349030b5e903 ('v1', 'v2', 'v3')
DETAIL:  prepare: SELECT CAST($1 AS TEXT) AS r1, CAST($2 AS TEXT) AS r2, CAST($1 AS TEXT) AS r3, CAST($2 AS TEXT) AS r4

ERROR:  wrong number of parameters for prepared statement "mdb2_statement_pgsql_208664a2f39741a37ff1c60380c0430d162a1ac36", Expected 2 parameters but got 3

MDB2_Driver_pgsql: Bug 18488 [Open] tableInfo doesn't return flags

kurtjos at gmail dot com — 2011-04-29T15:36:54+00:00

MDB2_Driver_pgsql Bug
Reported by kurtjos
2011-04-29T15:36:54+00:00
PHP: 5.3.1 OS: linux mint 10 Package Version: 1.5.0b3

Description:
------------
my phpinfo says:
PHP Version 5.3.3-1ubuntu9.3

postgresql version: 8.4.8

the table in question partial output from phppgsql:
Column    Type      Not Null  Default        Constraints
companyid integer   NOT NULL                 [pk]       

it has a default value of: 
nextval(('"company_companyid_seq"'::text)::regclass)


Test script:
---------------
function loadFields($table_name){
     global $mdb2;
     $tableinfo = array();
     
     $q    = "SELECT * FROM ".$table_name." LIMIT 1";
     $res  = $mdb2->query($q);
     $row  = $res->fetchRow();
     $cols = $res->getColumnNames(FLIP);
     
     $mdb2->loadModule('Extended');
     $mdb2->loadModule('Manager');
     
     $tableinfo = $mdb2->tableInfo($res,NULL);
     print_r("tableInfo: \n");      // my debug info
     print_r($tableinfo);           // my debug info
     
     return $cols;
}

Expected result:
----------------
tableInfo: 
Array
(
    [0] => Array
        (
            [table] => company
            [name] => companyid
            [type] => int4
            [length] => 4
            [flags] => not_null primary_key
            [mdb2type] => integer
        )


Actual result:
--------------
tableInfo: 
Array
(
    [0] => Array
        (
            [table] => company
            [name] => companyid
            [type] => int4
            [length] => 4
            [flags] => 
            [mdb2type] => integer
        )

MDB2_Driver_pgsql: Bug 17198 [Open] Loosing db-session properties after disconnect

felix_ant at gva dot es — 2010-03-08T14:41:54+00:00

MDB2_Driver_pgsql Bug
Reported by felix_ant
2010-03-05T21:15:11+00:00
PHP: 5.2.5 OS: 1.4.1 Package Version: 1.4.1

Description:
------------
We are working with Postgresql and using several connections. Always that we make a connection, we change some vars of the db-session (datestyle, client_encoding, ...). The problem appears when we disconnect one of them;  then , the rest of the connections loose the db-sessions var that we fixed previously.

We don't want to use "persistence connections", and we have read that the php-core optimizes no-persistence connections using the same instance with the same connection string. But we don't know why when you disconnect one of them, you are changing session enviroment of the rest.

It could be a bug or, is a mistake of ourselves?

Test script:
---------------
 'pgsql',
			'username' => 'xxxx',
			'password' => 'xxxx',
			'hostspec' => 'rosa.coput.gva.es',
			'database' => 'marte',
		);
		
$options = array(
    		'portability' => MDB2_PORTABILITY_NONE,
		);
$changeDateStyle = 'set session datestyle = \'sql, european\'';

$query = <<exec($changeDateStyle);
if (PEAR::isError($result))
	throw new Exception('Error setting datestyle...');		

//Second connection
$con2 = MDB2::connect($dsn,$options);
if (PEAR::isError($con2))
	throw new Exception('Error connecting...');    
$result = $con2->exec($changeDateStyle);
if (PEAR::isError($result))
	throw new Exception('Error setting datestyle...');


//Query with connect1
$resc1 = $con1->query($query);
if (PEAR::isError($resc1)){
	throw new Exception('Error launching query...');
}
$result1 = $resc1->fetchAll();
echo "Result with 1st connection\n";
print_r($result1);
$con1->disconnect();	

//Query with connect2
$resc2 = $con2->query($query);
if (PEAR::isError($resc2)){
	throw new Exception('Error launching query...');
}
$result2 = $resc2->fetchAll();
echo "\nResult with 2on connection\n";
print_r($result2);
$con2->disconnect();	

?>

Expected result:
----------------
Result with 1st connection
Array
(
    [0] => Array
        (
            [0] => 01/01/2003
        )

)

Result with 2on connection
Array
(
    [0] => Array
        (
            [0] => 01/01/2003
        )

)


Actual result:
--------------
Result with 1st connection
Array
(
    [0] => Array
        (
            [0] => 01/01/2003
        )

)

Result with 2on connection
Array
(
    [0] => Array
        (
            [0] => 2003-01-01
        )

)

MDB2_Driver_pgsql: Feature/Change Request 11802 [Open] Methods to check connection status and busy

pberry at stellaconcepts dot com — 2007-08-09T01:27:51+00:00

MDB2_Driver_pgsql Feature/Change Request
Reported by pberry
2007-08-09T01:27:51+00:00
PHP: Irrelevant OS: N/A Package Version: 1.4.1

Description:
------------
Neither the driver or MDB2 contains a way to manually 
check if a connection is still active and whether or not 
it's busy.

Two methods that I've added to MDB2_Driver_pgsql are 
connectionIsBusy() and pingConnection(), it would be nice 
if these or something similar could be rolled into main.

Test script:
---------------
function connectionIsBusy(){
   if(pg_connection_busy($this->connection)){
        return TRUE ;
   }
}

function pingConnection(){
 if(pg_connection_status($this->connection) === PGSQL_CONNECTION_OK){
     return TRUE ;
  }
}

MDB2_Driver_pgsql: Feature/Change Request 7059 [Open] pgsql error code mapping cannot handle localized error messages

sacher at manetmail dot de — 2006-03-12T09:13:56+00:00

MDB2_Driver_pgsql Feature/Change Request
Reported by sacher@...
2006-03-08T10:39:04+00:00
PHP: 5.0.4 OS: Linux SuSE10.0 i386 Package Version: 

Description:
------------
The documentation says that a sequence will automatically  be created on nextID(.., true). 

nextID returns a DB_Error like this:
DB Error: unknown error 
-1
SELECT NEXTVAL('test_seq') [nativecode=FEHLER:  Relation ÃÂ»test_seqÃÂ« existiert nicht]
(relation does not exist)

Reason seems to be the return code of the used PostgreSQL which is not the one expected by nextID().

If uncomment the condition in 
DB/pqsql.php Line 681 $result->getCode() == DB_ERROR_NOSUCHTABLE
everything works fine.

Used db is PostgreSQL 7.4.8