Skip to content

PDO_Firebird: Add connection level SESSION_TIMEZONE attribute #15480

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 8 commits into from
Closed

PDO_Firebird: Add connection level SESSION_TIMEZONE attribute #15480

wants to merge 8 commits into from

Conversation

sim1984
Copy link
Contributor

@sim1984 sim1984 commented Aug 18, 2024

This feature allows you to set the session time zone when connecting to the database. An alternative is to set the time zone after the connection is established using the query:

$dbh->exec("SET TIME ZONE '$timezone'");

Copy link
Member

@cmb69 cmb69 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you! This looks generally sensible to me.

@@ -14,15 +14,25 @@ define('PDO_FIREBIRD_TEST_DSN', getenv('PDO_FIREBIRD_TEST_DSN') ?: '');

if(!PDO_FIREBIRD_TEST_DSN)
{
die('Error: PDO_FIREBIRD_TEST_DSN must be set');
die('Error: PDO_FIREBIRD_TEST_DSN must be set');
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd stick with 4 spaces as indentation in PHP files, but I don't think we have any CS in this regard.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK

@sim1984
Copy link
Contributor Author

sim1984 commented Aug 20, 2024

I can't make an independent PR to clean up the code when there is an active PR. Now I know where I made a mistake. But it is not clear how to reassign a separate branch for an existing PR.

@cmb69
Copy link
Member

cmb69 commented Aug 20, 2024

Now I know where I made a mistake. But it is not clear how to reassign a separate branch for an existing PR.

Ah, I see. I suggest to just close this PR, and open up a new one.

@sim1984 sim1984 closed this Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants