You are right. I know of two languages that support HereDoc and NowDoc:
PHP and Ruby.
In PHP, you would use:
$myString=<<<EOS
.
.
.
EOS;
OR <<<‘EOS’;
In Ruby, you would use ‘<<’ instead of ‘<<<’.
You are right. I know of two languages that support HereDoc and NowDoc:
PHP and Ruby.
In PHP, you would use:
$myString=<<<EOS
.
.
.
EOS;
OR <<<‘EOS’;
In Ruby, you would use ‘<<’ instead of ‘<<<’.
go stored procedure
that is one thing that keeps me off mySQL and PHP to a certain extent
you have to be very aware of security issues here
when mySQL present something akin to stored procedures I will jump in
news flash… mysql version 5 supports stored procedures
mysql version 5 came out in beta in march 2005 and in production release in october 2005
the time is well overdue for you to jump in
Great discussion.
How much overhead will it create if a coder were to create an abstract layer that performed security checks on any data that was to be parsed to the database? What I mean is, if every form, or user input were to be passed to a security object that would then scrutinize the data before returning it to the database update routine, would it add significant overhead to the performance of the script?