MySQL Bugs: #52649: Feature request: ODBC read-only connection

Bug #52649	Feature request: ODBC read-only connection
Submitted:	7 Apr 2010 10:14	Modified:	7 Apr 2010 13:12
Reporter:	Mini Traktor	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	Connector / ODBC	Severity:	S4 (Feature request)
Version:		OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	ODBC, read-only

Description:
Request the ability to make a read-only connection to a data source through ODBC driver.

How to repeat:
1. Register an Excel document located on a server (i.e. another computer) in your local network as an ODBC data source

2. Open the Excel document on the server

3. Try using e.g. Sun's JDBC-ODBC bridge on the client computer to read from the Excel document

Resulting message: "It is already opened exclusively by another user, or you need permission to view its data"

The above message is given even when "READONLY=true" is written in the connection string.

Reading from the data source only works if the document is opened in read-only mode or if it is a shared workbook.

Suggested fix:
I want to read from the Excel document, not write anything to it. When I open the Excel file on my client computer (through the network) I get a message that it is locked for editing and an option to open it as a read-only file. Can it be made possible to do something similar with the ODBC connection - specifying that it should be a read-only connection?

Hi minitraktor, hehehehe

Sorry, but the nick is just fabulous.

Now, I do not get:
  3. Try using e.g. Sun's JDBC-ODBC bridge on the client computer to read from the Excel document

How do you exercise JDBC/ODBC bridge???? Whay not use just JDBC *or* ODBC?

Next, we wrote c/ODBC to allow access to data stored in MySQL server, not on file-system and some 3rd party closed source, proprietary... format.

Finally, and just because of great nick, I'll get someone to give second opinion but this is not a valid feature request by me.

Mini Traktor,
Sorry, but I don't see a place for MySQL c/odbc in your scheme. Nor I can see how c/odbc connection option could force efcel to open file read-only.

Thus I don't see this request valid unless you give us some more explanations. But so far I think this report should be closed.

Sorry Mini, !Bg nor valid feature request...