#35932 [Fbk->Opn]: PDO constructor failing on Windows 2000

ID: 35932 User updated by: j dot gizmo at aon dot at Reported By: j dot gizmo at aon dot at -Status: Feedback +Status: Open Bug Type: PDO related Operating System: Windows 2000 PHP Version: 5.1.1 New Comment: I was trying to connect to SQLite version 3. I tried different strings for $dsn, including: "sqlite:test.db" "sqlite::memory:" I used only the drivers that came with PHP 5.1.1. Previous Comments: ------------------------------------------------------------------------ [2006-01-11 17:11:46] dbs@php.net Changed summary to more accurately reflect bug report. ------------------------------------------------------------------------ [2006-01-11 17:07:28] dbs@php.net In addition to trying the latest release snapshot, please provide more information: What PDO driver are you using? What database (including version) are you connecting to? What is the value of $dsn that you are passing to the PDO constructor? ------------------------------------------------------------------------ [2006-01-08 17:13:36] tony2001@php.net Please try using this CVS snapshot: http://snaps.php.net/php5.1-latest.tar.gz For Windows: http://snaps.php.net/win32/php5.1-win32-latest.zip ------------------------------------------------------------------------ [2006-01-08 17:00:56] j dot gizmo at aon dot at In fact, I just found out that according to the online documentation, the syntax used in the docs is in fact correct. However, the correct syntax does not work on PHP 5.1.1 on Win2K; so it is more a PDO related issue than documentation related. ------------------------------------------------------------------------ [2006-01-08 16:59:13] nlopess@php.net this is not a documentation problem surely. PHP 5 deprecates the use of '=& new' syntax, as objects are always references. Please try with latest PHP 5 version available and if the problem persists, reopen this bug, but not as a documentation problem. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/35932 -- Edit this bug report at http://bugs.php.net/?id=35932&edit=1