You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by Daniel Rall <dl...@finemaltcoding.com> on 2001/04/25 02:13:59 UTC

Re: cvs commit: jakarta-turbine/conf/torque/templates/sql/security default-roles-perms.vm default-secure-passwords.vm

jon@apache.org writes:

> jon         01/04/24 15:42:37
> 
>   Modified:    conf/torque/templates/sql/security default-roles-perms.vm
>                         default-secure-passwords.vm
>   Log:
>   use # instead of -- or /* */ as it seems like it is more portable for
>   mysql...dunno if this breaks other databases though...

I thought that "-- " was the most portable.  Comments?

---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org


Re: cvs commit: jakarta-turbine/conf/torque/templates/sql/security

Posted by Daniel Rall <dl...@finemaltcoding.com>.
"Henning P. Schmiedehausen" <ma...@hometree.net> writes:

> Travis Low <tr...@dawnstar.org> writes:
> 
> >Dan said "-- ", not "--".  "-- " is the most portable (as well as the butt-ugliest).
> 
> And I said:
> 
> >> MySQL 3.23.3 and above supports the `--' comment style only if the
> >> comment is followed by a space. This is because this degenerate
> 
> there are lots and lots of 3.22 installations out there. All of them break.
> 
> Use /* */

We had reports on the Scarab list of /* */ not working under certain
Windows configurations...

---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org


Re: cvs commit: jakarta-turbine/conf/torque/templates/sql/security

Posted by Bruno Unna <br...@iac.com.mx>.
Jon Stevens wrote:

> on 4/25/01 9:03 AM, "Henning P. Schmiedehausen" <ma...@hometree.net>
> wrote:
> 
> 
>> Use /* */
>> 
>> Regards
>> Henning
> 
> 
> Right, but I don't think /* */ is portable either...
> 

For PostgreSQL (at least for the 7.1 version) both types of comments do 
work, but in previous versions *the* way to comment was with "--".

 From the official documentation of 7.1:

--- 8< ---
A comment is an arbitrary sequence of characters beginning with double 
dashes and extending to the end of the line, e.g.:

-- This is a standard SQL92 comment

Alternatively, C-style block comments can be used:

/* multi-line comment
  * with nesting: /* nested block comment */
  */
where the comment begins with /* and extends to the matching occurrence 
of */. These block comments nest, as specified in SQL99 but unlike C, so 
that one can comment out larger blocks of code that may contain existing 
block comments.

A comment is removed from the input stream before further syntax 
analysis and is effectively replaced by whitespace.
--- 8< ---


---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org


BEA Weblogic 6

Posted by Gareth Coltman <ga...@majorband.co.uk>.
Hi!

I know some of you guys have used BEA Weblogic before, so I wonder if you
know why I might get the following exception when trying to access my
servlet:

org.apache.turbine.services.InstantiationException: ServiceBroker: unknown
servi
ce TurbinePoolService requested
        at
org.apache.turbine.services.BaseServiceBroker.getServiceInstance(Base
ServiceBroker.java:312)
        at
org.apache.turbine.services.BaseServiceBroker.getService(BaseServiceB
roker.java:257)
        at
org.apache.turbine.util.RunDataFactory.putRunData(RunDataFactory.java
:230)
        at org.apache.turbine.Turbine.doGet(Turbine.java:488)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:213)
        at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:1265)
        at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:1622)
        at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)


DETAILS:

Weblogic 6 on W2K

It seems to me that the TurbineResources.props file wasn't loaded. I have
tried using both a relative (to the current dir and also the docbase) and
absolute paths to specify it in the web.xml file.

            <param-name>properties</param-name>
            <!-- This is relative to the docBase -->

<param-value>/bea/wlserver6.0sp1/config/rightmove/applications/devsite/WEB-I
NF/conf/TurbineResources.props
</param-value>

Also tried using a windows path like C:\asksak\skadaskjlsdakl\jkasdk

but no joy.

Has anyone experienced similar problems?

Gareth


---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org


Re: cvs commit: jakarta-turbine/conf/torque/templates/sql/security

Posted by Jon Stevens <jo...@latchkey.com>.
on 4/25/01 9:03 AM, "Henning P. Schmiedehausen" <ma...@hometree.net>
wrote:

> Use /* */
> 
> Regards
> Henning

Right, but I don't think /* */ is portable either...

-jon


---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org


Re: cvs commit: jakarta-turbine/conf/torque/templates/sql/security

Posted by Jon Stevens <jo...@latchkey.com>.
on 4/25/01 9:03 AM, "Henning P. Schmiedehausen" <ma...@hometree.net>
wrote:

> Use /* */
> 
> Regards
> Henning

Ok, Oracle supports /* */

You need to register to see this...but...

<http://technet.oracle.com/doc/server.815/a67779/ch2.htm#31715>

Comments Within SQL Statements

Comments within SQL statements do not affect the statement execution, but
they may make your application easier for you to read and maintain. You may
want to include a comment in a statement that describes the statement's
purpose within your application.

A comment can appear between any keywords, parameters, or punctuation marks
in a statement. You can include a comment in a statement using either of
these means: 

*    Begin the comment with a slash and an asterisk (/*). Proceed with the
text of the comment. This text can span multiple lines. End the comment with
an asterisk and a slash (*/). The opening and terminating characters need
not be separated from the text by a space or a line break.
*    Begin the comment with -- (two hyphens). Proceed with the text of the
comment. This text cannot extend to a new line. End the comment with a line
break. 

A SQL statement can contain multiple comments of both styles. The text of a
comment can contain any printable characters in your database character set.

Can other people confirm that their database supports /* */?

-jon


---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org


Re: cvs commit: jakarta-turbine/conf/torque/templates/sql/security

Posted by "Henning P. Schmiedehausen" <ma...@hometree.net>.
Travis Low <tr...@dawnstar.org> writes:

>Dan said "-- ", not "--".  "-- " is the most portable (as well as the butt-ugliest).

And I said:

>> MySQL 3.23.3 and above supports the `--' comment style only if the
>> comment is followed by a space. This is because this degenerate

there are lots and lots of 3.22 installations out there. All of them break.

Use /* */

	Regards
		Henning



-- 
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen       -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH     hps@intermeta.de

Am Schwabachgrund 22  Fon.: 09131 / 50654-0   info@intermeta.de
D-91054 Buckenhof     Fax.: 09131 / 50654-20   

---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org


Re: cvs commit: jakarta-turbine/conf/torque/templates/sql/security default-roles-perms.vm default-secure-passwords.vm

Posted by Travis Low <tr...@dawnstar.org>.
Dan said "-- ", not "--".  "-- " is the most portable (as well as the butt-ugliest).

T

"Henning P. Schmiedehausen" wrote:
> 
> Daniel Rall <dl...@finemaltcoding.com> writes:
> 
> >jon@apache.org writes:
> 
> >> jon         01/04/24 15:42:37
> 
> >>   use # instead of -- or /* */ as it seems like it is more portable for
> >>   mysql...dunno if this breaks other databases though...
> 
> >I thought that "-- " was the most portable.  Comments?
> 
> --- cut ---
> MySQL manual, section 5.4.7:
> 
> Some other SQL databases use `--' to start comments. MySQL has `#' as
> the start comment character, even if the mysql command line tool
> removes all lines that start with `--'. You can also use the C comment
> style /* this is a comment */ with MySQL. See section 7.29 Comment
> syntax.
> 
> MySQL 3.23.3 and above supports the `--' comment style only if the
> comment is followed by a space. This is because this degenerate
> comment style has caused many problems with automatically generated
> SQL queries that have used something like the following code, where we
> automatically insert the value of the payment for !payment!:
> 
> UPDATE tbl_name SET credit=credit-!payment!
> 
> What do you think will happen when the value of payment is negative?
> 
> Because 1--1 is legal in SQL, we think it is terrible that `--' means
> start comment.
> --- cut ---
> 
> ==> Use /* */
> 
>         Regards
>                 Henning
> 
> --
> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen       -- Geschaeftsfuehrer
> INTERMETA - Gesellschaft fuer Mehrwertdienste mbH     hps@intermeta.de
> 
> Am Schwabachgrund 22  Fon.: 09131 / 50654-0   info@intermeta.de
> D-91054 Buckenhof     Fax.: 09131 / 50654-20
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org

-- Travis Low  
   <ma...@dawnstar.org>
   <http://dawnstar.org/travis>

---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org


Re: cvs commit: jakarta-turbine/conf/torque/templates/sql/security default-roles-perms.vm default-secure-passwords.vm

Posted by "Henning P. Schmiedehausen" <ma...@mail.hometree.net>.
Daniel Rall <dl...@finemaltcoding.com> writes:

>jon@apache.org writes:

>> jon         01/04/24 15:42:37

>>   use # instead of -- or /* */ as it seems like it is more portable for
>>   mysql...dunno if this breaks other databases though...

>I thought that "-- " was the most portable.  Comments?

--- cut ---
MySQL manual, section 5.4.7:

Some other SQL databases use `--' to start comments. MySQL has `#' as
the start comment character, even if the mysql command line tool
removes all lines that start with `--'. You can also use the C comment
style /* this is a comment */ with MySQL. See section 7.29 Comment
syntax.

MySQL 3.23.3 and above supports the `--' comment style only if the
comment is followed by a space. This is because this degenerate
comment style has caused many problems with automatically generated
SQL queries that have used something like the following code, where we
automatically insert the value of the payment for !payment!:

UPDATE tbl_name SET credit=credit-!payment!

What do you think will happen when the value of payment is negative?

Because 1--1 is legal in SQL, we think it is terrible that `--' means
start comment.
--- cut ---


==> Use /* */

	Regards
		Henning

-- 
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen       -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH     hps@intermeta.de

Am Schwabachgrund 22  Fon.: 09131 / 50654-0   info@intermeta.de
D-91054 Buckenhof     Fax.: 09131 / 50654-20   

---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org