I have the following code:

  MyDModule.ConfigurationQuery.SQL.Clear;
  MyDModule.ConfigurationQuery.SQL.Text :=
  'GRANT ALL PRIVILEGES ON DATABASE ' + Engine.QuotedSQLStr(DATABASE_NAME)
+
  ' TO ' + DATABASE_ADMIN_USER;
  try
  MyDModule.ConfigurationQuery.ExecSQL;
  finally
  MyDModule.ConfigurationQuery.Close;
  end;

The database name is a constant and is a name without spaces.

I get an exception that the SQL is expecting the name of the database.

If I remove the quotedSQLStr, then it work.

I guess the question is...  what if this wasn't a constant and the customer
created a database with a space?

My expectation would be that if I took a safe approach and put double qoutes
around it, it would work, regardless.

I notice this behaviour as well when creating users.   I would expect that I
could doubleqoute the user name and password in case the user uses spaces.

Lance

Lance


Quick cut from the manual

"QuotedSQLStr method to properly format and escape any embedded single quotes in the string."

You need double quotes (I think)

Roy Lambert

Lance,

<< If I remove the quotedSQLStr, then it work. >>

Roy is correct - QuotedSQLStr only deals with literals enclosed in
single-quotes.

--
Tim Young
Elevate Software
www.elevatesoft.com

Well don't that beat all.....  How about <possiblestringwithspace>
</possiblestringwithspace>  XML capability instead....   

Thanks Roy / Tim!







"Lance Ras" <lance@cdesoftware.com> wrote in message
news:D47FA3C6-7A74-4007-B302-CB72461788C1@news.elevatesoft.com...
>I have the following code:
>
>   MyDModule.ConfigurationQuery.SQL.Clear;
>   MyDModule.ConfigurationQuery.SQL.Text :=
>   'GRANT ALL PRIVILEGES ON DATABASE ' + Engine.QuotedSQLStr(DATABASE_NAME)
> +
>   ' TO ' + DATABASE_ADMIN_USER;
>   try
>   MyDModule.ConfigurationQuery.ExecSQL;
>   finally
>   MyDModule.ConfigurationQuery.Close;
>   end;
>
> The database name is a constant and is a name without spaces.
>
> I get an exception that the SQL is expecting the name of the database.
>
> If I remove the quotedSQLStr, then it work.
>
> I guess the question is...  what if this wasn't a constant and the
> customer created a database with a space?
>
> My expectation would be that if I took a safe approach and put double
> qoutes around it, it would work, regardless.
>
> I notice this behaviour as well when creating users.   I would expect that
> I could doubleqoute the user name and password in case the user uses
> spaces.
>
> Lance