[
http://jira.codehaus.org/browse/MSQL-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155015#action_155015
]
struberg edited comment on MSQL-29 at 11/21/08 3:20 PM:
-------------------------------------------------------------
Hi Dan!
The reason why I introduced an own parameter is the following:
I'm not sure if there aren't any JDBC drivers/database combinations which check
for the presence of the password parameter (even if it's empty), and those will
then be broken.
I'm not sure which combination it was (might be postgreSQL or DB/2, I'm not
sure), but my gut feeling tells me that there was something like this. And so I
decided to do a very defensive implementation.
Maybe we should rename the parameter to something more verbose like
'omitEmptyPassword'?
Another option would be to make your suggestion the default behaviour and add
an option 'sendEmptyPassword'?
LieGrue,
strub
was (Author: struberg):
Hi Dan!
The reason why I introduced an own parameter is the following:
I'm not sure if there aren't any JDBC drivers/database combinations which check
for the presence of the password parameter (even if it's empty), and those will
then be broken.
I'm not sure which combination it was (might be postgreSQL or DB/2, I'm not
sure), but my gut feeling tells me that there was something like this. And so I
decided to do a very defensive implementation.
Maybe we should rename the parameter to something more verbose like
'omitEmptyPassword'?
LieGrue,
strub
> Allow anonymous access (connecting to database without password)
> ----------------------------------------------------------------
>
> Key: MSQL-29
> URL: http://jira.codehaus.org/browse/MSQL-29
> Project: Maven 2.x SQL Plugin
> Issue Type: New Feature
> Affects Versions: 1.3
> Environment: linux-2.6.27.5-117.fc10.x86_64, MySQL-5.0.67
> Reporter: Mark Struberg
> Assignee: Dan Tran
> Attachments: sql-anonymous.patch
>
>
> Some databases do not allow connecting the database with password="".
> E.g. MySQL fails if it gets an empty password property in the connection
> initialisation sequence:
> {noformat}
> Access denied for user 'root'@'localhost' (using password: YES)
> {noformat}
> So we may provide an option "anonymous" which simply skips adding the
> password property when connecting.
> (And please argue with me that one should _never_ use a database without a
> password! Really, *I* see this exactly as you do and explained the reasons
> until I got blue in my face, but finally I capitulated)
> The attached patch adds the 'anonymous' option handling.
> It has been tested on 2 other setups (F9, Ubuntu) also.
> txs and LieGrue,
> strub
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
