Hi.
I've got this file:
foo
foo
Which when served to the browser is sent
as:
foo
foo
>
This shows the input field as a real text entry field
on the screen, and has the spurious > on the end.
I know the HTML in the comment is dodgy, but I expected it
to be ignore as it's
>
> I know the HTML in the comment is dodgy, but I expected it
> to be ignore as it's in a comment...
>
The html comment is parsed nevertheless because it can contain Perl blocks,
which has to be executed.
Change the html comment to an Embperl comment ( [# ... #] ) and everything
should be fine.
Below is the code that I have written to handle the case of when the user
selects the update button on the form. The update button is of type submit.
I
assume that what is in fdat are all the items that are on the form. I have
created an array that holds the names of each of the form elements:
Hi Gerald,
I am in the process of writing my own Perl Apache modules, and wondered
if you have any tips or resources related to making a more professional
installation package. I think you use something called MakeMaker, for
example.
In a nutshell, I want people to be able to download the tarbal
I am trying to use !TabRelation in the following manner:
#---
# reterive all notes for this incident ordered by date
#---
DBIx::Recordset::Undef ('set');
$fdat{'!DataSource'} = GetDSN();
$fdat{'!Table'}= 'note, unane
...
> fdat{note.employee_key} = 1
...
> fdat{note.note_datetime} = 8/29/2001
> fdat{note.note_key} = 10037
> fdat{note.incident_key} = 10149
The above values of %fdat, are made to the where expression by
DBIx::Recordset. You only pass %fdat to Execute not to Search, that's the
difference:
> DB:
>
> I am in the process of writing my own Perl Apache modules, and wondered
> if you have any tips or resources related to making a more professional
> installation package. I think you use something called MakeMaker, for
> example.
>
Yes, every Perl module uses MakeMaker, see
perldoc ExtUtils::
> DB: 'SELECT unanet_employee.first_name || ' ' ||
unanet_employee.last_name
> as employee_name,
> note.note_datetime,
> note.note
>FROM note, unanet_employee
>WHERE (unanet_employee.employee_key = note.employee_key) and
>
I understand that it does not make a difference when you run the raw SQL
against the database. but for some reason it makes a difference when it is
run under EmbPerl. the first one does not return a record set while the
second one does.
-Original Message-
From: Gerald Richter [mailto:
If I understand you correctly. When you use DBIx with an excute it makes
use of what is in %fdat even though
I did not do a $fdat{!Fields'} or $fdat('$fields'} statement. if that is
the case then there seems to be a problem with using
DBIx. I can see why using the search does not have a proble
> I understand that it does not make a difference when you run the raw SQL
> against the database. but for some reason it makes a difference when it
is
> run under EmbPerl. the first one does not return a record set while the
> second one does.
>
Then there must be another reason, but the SQL i
Hi,
When I enter some data via a form to test.html it's all OK.
But how can I get posted data like $ENV{'QUERY_STRING'} when I use get
method?
Thanks.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mai
> If I understand you correctly. When you use DBIx with an excute it makes
> use of what is in %fdat even though
> I did not do a $fdat{!Fields'} or $fdat('$fields'} statement. if that is
> the case then there seems to be a problem with using
> DBIx. I can see why using the search does not have
Hi,
>
> When I enter some data via a form to test.html it's all OK.
> But how can I get posted data like $ENV{'QUERY_STRING'} when I use get
> method?
>
Embperl makes all data, regardless if POST or GET, available in %fdat.
If this was not your question, please explain it a little bit more
Ge
This is correct I am passing %fdat to Execute.
>From the documentation, I was expecting that Execute would only look at
those items
that have been identified using the defined parameters as stated in the
document. That
is Execute should only be looking at fields that have been identified with
!F
Hi,
I'm having trouble passing arrays to Execute.
Passing parameters to my page component:
Execute ({inputfile =>
$CSI_common."displayresponder.html", param
=> [$bgcolor1,$bgcolor2,$textcolor,@records]});
Reading the parameters in my page component:
[-
$bgcolor1 = $param[0
Hey John,
I'll reply as I've just finished fighting through learning how to pass
scalers and hashes via param. I'd have responded sooner if you hadn't
posted in email, though.
I believe you need two pass your @records array by reference.
Pass the parameters:
[-
@records = qw(one two three);
John,
Try passing your params as references to the actual variables - remember,
paramaters are all "mushed" into a single array when they are passed, so by
using references, and de-referencing them, you can disentangle the
individual variables easily.
Ken Ray
>Hi,
>
>I'm having trouble passi
[root@dreamserver temp]# www configtest
Syntax error on line 803 of /usr/local/apache/conf/httpd.conf:
Invalid command 'PerlHandler', perhaps mis-spelled or defined by a module
not included in the server configuration
I installed apache_1.3.9 with mod_perl-1.26. It was then followed up
HTML-Embp
19 matches
Mail list logo
