Skip to content
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

Calling sqlsrv_connect() with TraceFile set but TraceOn set to False creates an empty file. #13

Closed
v-mabarw opened this issue Jul 29, 2014 · 0 comments

Comments

@v-mabarw
Copy link
Member

Hi.

Just started playing with this extension in earnest.

__FILE__, 'CharacterSet' => 'UTF-8', 'ConnectionPooling' => True, 'Database' => 'My_DB', 'Encrypt' => False, 'Failover_Partner' => '', 'LoginTimeout' => 10, 'MultipleActiveResultSets' => True, 'PWD' => 'My_PWD', 'QuotedId' => True, 'ReturnDatesAsStrings' => False, ``` // 'TraceFile' => 'Z:/Logs/SQLTrace/' . date('Y-m-d G.i.s ') . basename( ** FILE *\* ) . '_Trace.log', ``` 'TraceOn' => False, 'TransactionIsolation' => SQLSRV_TXN_READ_COMMITTED, 'TrustServerCertificate' => True, 'UID' => 'My_UID', 'WSID' => getenv('COMPUTERNAME'), ) ); ``` ?>

The call works fine, but if I don't comment out 'TraceFile', I get a zero
length file.

I think the file should be created when the first trace entry is written. If
no tracing is actually written (the TraceOn is False), then nothing should be
created.

Regards,

Richard Quadling.

Work Item Details

Original CodePlex Issue: Issue 16928
Status: Closed
Reason Closed: Unassigned
Assigned to: Unassigned
Reported on: Mar 23, 2010 at 3:32 PM
Reported by: RQuadling
Updated on: Jul 17, 2010 at 8:28 PM
Updated by: AshayC
Closed on: Jul 17, 2010 at 8:28 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant