List:General Discussion« Previous MessageNext Message »
From:Rhino Date:May 7 2006 1:46pm
Subject:Re: PRINT statement?
View as plain text  
----- Original Message ----- 
From: "Stephen Cook" <sclists@stripped>
To: "MySQL List" <mysql@stripped>
Sent: Sunday, May 07, 2006 3:53 AM
Subject: PRINT statement?


> Is there a statement similar to PRINT in T-SQL (MicroSoft SQL Server)?
>
> It would be handy to debug some scripts.
>
If you're talking about a script that is running SQL, you can simply use the 
SELECT statement without any FROM, WHERE, ORDER BY, GROUP BY or HAVING 
clauses. For example:

    select "Creating Foo table" as "Action";

will produce the following output:

    +----------------------+
    | Action                   |
    +----------------------+
    | Creating Foo table |
    +----------------------+
    1 row in set (0.00 sec)

If you're talking about an OS script, you can use OS commands to display 
things. For example, I have some BASH scripts on our Linux server so I can 
use the BASH echo command, like this:

    #!/bin/bash
    report_date=`/bin/date`
    echo "Report Date:" $report_date;

to produce this output:

    Report Date: Sun May 7 09:42:57 EDT 2006


--
Rhino
 



-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.392 / Virus Database: 268.5.5/333 - Release Date: 05/05/2006

Thread
PRINT statement?Stephen Cook7 May
  • Re: PRINT statement?Rhino7 May
    • Re: PRINT statement?Stephen Cook11 May
  • Re: PRINT statement?Rhino11 May
RE: PRINT statement?Quentin Bennett11 May
  • Re: PRINT statement?Rhino11 May
    • Re: PRINT statement?Stephen Cook12 May
      • Re: PRINT statement?Peter Brawley12 May
        • Re: PRINT statement?Stephen Cook12 May
          • Re: PRINT statement?Mark Leith12 May
            • MySQL commercial licenceAdam Lipscombe12 May
              • Re: MySQL commercial licenceDavid Logan12 May
                • RE: MySQL commercial licenceAdam Lipscombe12 May
                  • Re: MySQL commercial licencesheeri kritzer12 May
          • Re: PRINT statement?Peter Brawley12 May
            • Re: PRINT statement?Stephen Cook13 May