You are viewing a plain text version of this content. The canonical link for it is here.
Posted to embperl@perl.apache.org by Richard Schilling <rs...@nationalinformatics.net> on 2003/09/14 02:28:05 UTC

A TABLE-processing-with-[$ while $]-blocks-involved question

Just got done debugging an application that used the following form:

<TABLE WIDTH="100%">
<TR>
         <TH>Contract ID</TH>
         <TH>Start Timestamp</TH>
         <TH>End Timestamp</TH>
         <TH>Minimum Hours Quoted</TH>
         <TH>Maximum Hours Quoted</TH>
         <TH>Minimum Fees Quoted</TH>
         <TH>Maximum Fees Quoted</TH>
         <TH>Status</TH>
  </TR>
  [$ while @contractinfo=$rsmbacontracts->fetchrow $]
<TR>
         <TD>[+ $contractinfo[0] +]</TD>
         <TD>[+ $contractinfo[2] +]</TD>
         <TD>[+ $contractinfo[3] +]</TD>
         <TD>[+ $contractinfo[4] +]</TD>
         <TD>[+ $contractinfo[6] +]</TD>
         <TD>[+ $contractinfo[5] +]</TD>
         <TD>[+ $contractinfo[7] +]</TD>
         <TD>[+ $contractinfo[8] +]</TD>
</TR>
</TABLE>

[$ endwhile $]



The postgres log reported the following for the rsmbacontracts query:

LOG:  query: SELECT * FROM clientcontracts WHERE accountguid = 
'b6ea9cafe2d1997392d166b96e5697b1';
LOG:  pq_recvbuf: unexpected EOF on client connection


=======

I tried and tried to figure out what was wrong, and then it hit me: the 
[$ endwhile $] command needs to appear *before* the </TABLE> tag.

So, what happened?


I suspect it has to do with Embperl table processing, but am curious 
about the internals.

Richard Schilling
rsmba.biz

---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org


Re: DBIx::Recordset status

Posted by Terrence Brannon <tb...@directsynergy.com>.
----- Original Message -----
From: "Gerald Richter" <ri...@ecos.de>
To: "Angus Lees" <gu...@debian.org>; "Terrence Brannon"
<tb...@directsynergy.com>
Cc: <em...@perl.apache.org>
Sent: Wednesday, October 08, 2003 9:23 AM
Subject: Re: DBIx::Recordset status


> Hi,
>
> it's true DBIx::Recordset hasn't been updated for a long time. The reason
is
> simple, it does all I need :-) Anyway I have a set of patches people send
me
> and it would be worth putting them into a new release. Also there are some
> ideas what can be enhanced. As you already know I don't have the time to
do
> it right now and when I have time I like to put it into Embperl to get 2.0
> finaly done.
>
> So maybe somebodyelse could help in maintaining DBIx::Recordset (or take
> over the maintainance). I can setup a public CVS (or better svn) which
holds
> the sources, so it should be quite easy to cooperate.

I don't know svn, but it is gaining in popularity, so I would be happy to
learn svn and add patches to recordset as requested.

>
> I think the work Angus has already done for the Debian release is a good
> starting point. Also the docs Terrence has written should be considered to
> be included

yes, DBIx::Recordset::Playground is designed around DBSchema::Sample, so
that people can actually run code when reading the docs instead of just
reading docs.

>
> Anybody likes to give it a try?

I will help out however I can. I have a good amount of free time on my
hands.




---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org


Re: DBIx::Recordset - DataSource => $DSN fails in test.pl

Posted by Gerald Richter <ri...@ecos.de>.
Terrence Brannon wrote:
> *** I plan to fix this my using the created $dbh in DoTest()
> throughout test.pl instead of passing $DSN to each independent
> Search() call, but thought I would report this.

$DSN is intentionaly passed to every Search. This normaly causes to have not
only one database connection (which seems the problem for Pg). This is done
to get a fresh start for a new test and not any cached values from the
previous test.

> I am further down in
> the test suite,
> getting it to truly pass for DBD::Pg, and have run across this error:
>
> Select dbixrs2.name2 id=id...
> --------------------
> WARN: DBI connect('dbname=test','metaperl',...) failed: could not
> connect to server: Address already in use at
> blib/lib/DBIx/Recordset.pm line 203
>

This seems to be the same problem, that Pg allows not two connections at the
same time. There are places in the test which uses two connections, one for
updateing and one for verfying, otherwise you can't make sure that things
are really written to the database and not only held in memory be
DBIx::Recordset

Gerald


> DB:  ERROR open DB dbi:Pg:dbname=test (could not connect to server:
> Address already in use)
> DB:  New Recordset driver=  placeholders supported
> DB:  FLUSH Recordset id = 7  DBIx::Recordset=HASH(0x10547af8)
> DB:  Disconnect (id=7, numOpen = 1)
> DB:  DESTROY (id=7, numOpen = 1)
> CHK-IDS: 2
> ERROR in Select dbixrs2.name2 id=id
> Got too few rows (got 0, expected 1)
> Select dbixrs2.value2 id=id...
>
> *** Which  corresponds to this code:
>
>  printlogf "Select $Table[1].name2 id=id";
>         print LOG "\n--------------------\n" ;
>
>         *set1_ = DBIx::Recordset -> Search ({  '!DataSource'   =>
>                                             $DSN, '!Username'     =>
>                                             $User, '!Password'     =>
>                                             $Password, '!Table'
> => "$Table[0], $Table[1]",
>                                             '!Fields'       =>
> "$Table[0].id, $Table[0].name, $Table[0].value1, $Table[0].addon",
>                                            "'$Table[1].name2" =>
> 'Second Name in Tab2',
>                                            "\\$Table[0].id" =>
> "$Table[1].id",
>                                            '$operator'=>'='})  or die
> "not ok ($DBI::errstr)" ;
>
> *** also note: I just committed my changes to test.pl back to svn up
> to this point:
>
>         ~/hacks/dbirs $ svn commit --message 'incremental commit while
> fixing test suite for DBD::Pg'
> Sending        test.pl
> Transmitting file data .
> Committed revision 143.
>         ~/hacks/dbirs $
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
> For additional commands, e-mail: embperl-help@perl.apache.org

--------------------------------------------------------------
Gerald Richter     ecos electronic communication services gmbh
IT-Securitylösungen * dynamische Webapplikationen * Consulting

Post:       Tulpenstrasse 5          D-55276 Dienheim b. Mainz
E-Mail:     richter@ecos.de          Voice:   +49 6133 939-122
WWW:        http://www.ecos.de/      Fax:     +49 6133 939-333
--------------------------------------------------------------
|
|   ECOS BB-5000 Firewall- und IT-Security Appliance: www.bb-5000.info
|
+-------------------------------------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org


DBIx::Recordset - DataSource => $DSN fails in test.pl

Posted by Terrence Brannon <me...@urth.org>.
*** I plan to fix this my using the created $dbh in DoTest() throughout 
test.pl instead of passing $DSN to each independent Search() call, but 
thought I would report this. I am further down in the test suite, 
getting it to truly pass for DBD::Pg, and have run across this error:

Select dbixrs2.name2 id=id...         
--------------------
WARN: DBI connect('dbname=test','metaperl',...) failed: could not 
connect to server: Address already in use at blib/lib/DBIx/Recordset.pm 
line 203

DB:  ERROR open DB dbi:Pg:dbname=test (could not connect to server: 
Address already in use)
DB:  New Recordset driver=  placeholders supported
DB:  FLUSH Recordset id = 7  DBIx::Recordset=HASH(0x10547af8)
DB:  Disconnect (id=7, numOpen = 1)
DB:  DESTROY (id=7, numOpen = 1)
CHK-IDS: 2
ERROR in Select dbixrs2.name2 id=id
Got too few rows (got 0, expected 1)
Select dbixrs2.value2 id=id...        

*** Which  corresponds to this code:

 printlogf "Select $Table[1].name2 id=id";
        print LOG "\n--------------------\n" ;

        *set1_ = DBIx::Recordset -> Search ({  '!DataSource'   =>  $DSN,
                                            '!Username'     =>  $User,
                                            '!Password'     =>  $Password,
                                            '!Table'        =>  
"$Table[0], $Table[1]",
                                            '!Fields'       =>  
"$Table[0].id, $Table[0].name, $Table[0].value1, $Table[0].addon",
                                           "'$Table[1].name2" => 'Second 
Name in Tab2',
                                           "\\$Table[0].id" => 
"$Table[1].id",
                                           '$operator'=>'='})  or die 
"not ok ($DBI::errstr)" ;

*** also note: I just committed my changes to test.pl back to svn up to 
this point:

        ~/hacks/dbirs $ svn commit --message 'incremental commit while 
fixing test suite for DBD::Pg'
Sending        test.pl
Transmitting file data .
Committed revision 143.
        ~/hacks/dbirs $




---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org


Re: DBIx::Recordset - nonsense query formation

Posted by Gerald Richter <ri...@ecos.de>.
>         $set6 -> Search ({"+$t0\lid|$t0\laddon"     =>  "6\tit",
>                           "$t0\lname"          =>  'Fourth Name',
>                           "\*$t0\lid"           =>  '>',
>                           "\*$t0\laddon"        =>  '<>',
>                           "\*$t0\lname"         =>  '=',
>                           '$compconj'     =>  'and',
>                           '$conj'         =>  'or' }) or die "not ok
> ($DBI::errstr)" ;
>
>
> The SELECT query generated by this:
>
>       DB:  'SELECT id, name, txt FROM dbixrs1, dbixrs3 WHERE
> (dbixrs1.value1=dbixrs3.value1) and (  (  (  id > ? and addon <> ?)
> or (  id > ? and addon <> ?)) or (  (name = ?)))      '
> bind_values=<6 6 it
> it Fourth Name> bind_types=<4 1 4 1 1>
>
> does not make sense because the SQL attempts to do this comparison:
>
>     id > it
>

Yes, it does not make to much sense, but this is a test for the construction
of the where expression, not a database test. For example in mysql this test
works without problems. Pg is somehow more strict, so some of the test
aren't performed for Pg.

The SQL is construced ok, that's all what the test should do

Gerald




> ...that's right, it attempts to compare a numerical field to the
> string "it" which rightly yields an error under Postgres.
>
> I'm going to go ahead and fix this, but thought I would report this as
> something I perceive as needing to be fixed.
>
> Here is test.log for this particular Search():
>
> Search $compconj...
> --------------------
> DB:  SelectWhere <*addon>=<<>> type = *
> DB:  SelectWhere <*id>=<>> type = *
> DB:  SelectWhere <+id|addon>=<6    it> type = +
> DB:  Composite Field +id|addon
> DB:  Composite Field processing id
> DB:  Composite Field get   id > ?
> DB:  Composite Field processing addon
> DB:  Composite Field get   id > ? and addon <> ?
> DB:  Key +id|addon gives   (  id > ? and addon <> ?)  or  (  id > ?
> and addon <> ?) bind_values = <6 6 it it> bind_types=<4 1 4 1>
> DB:  expr is   (  (  id > ? and addon <> ?)  or  (  id > ? and addon
> <> ?)) DB:  SelectWhere <$conj>=<or> type = $
> DB:  SelectWhere <*name>=<=> type = *
> DB:  SelectWhere <name>=<Fourth Name> type = n
> DB:  Single Field name
> DB:  Single Field gives name = ?
> DB:  Key name gives   (name = ?) bind_values = <6 6 it it Fourth Name>
> bind_types=<4 1 4 1 1>
> DB:  expr is   (  (  id > ? and addon <> ?)  or  (  id > ? and addon
> <> ?)) or (  (name = ?))
> DB:  SelectWhere <$compconj>=<and> type = $
> DB:  FLUSH Recordset id = 12  DBIx::Recordset=HASH(0x1054af98)
> DB:  Row::DESTROY
> DB:  Row::DESTROY
> DB:  Row::DESTROY
> DB:  Row::DESTROY
> DB:  Row::DESTROY
> DB:  Row::DESTROY
> DB:  Row::DESTROY
> DB:  Row::DESTROY
> DB:  Row::DESTROY
> DB:  Row::DESTROY
> DB:  Row::DESTROY
> DB:  'SELECT id, name, txt FROM dbixrs1, dbixrs3 WHERE
> (dbixrs1.value1=dbixrs3.value1) and (  (  (  id > ? and addon <> ?)
> or (  id > ? and addon <> ?)) or (  (name = ?)))      '
> bind_values=<6 6 it
> it Fourth Name> bind_types=<4 1 4 1 1>
> WARN: DBD::Pg::st execute failed: ERROR:  pg_atoi: error in "it":
> can't parse "it" at blib/lib/DBIx/Recordset.pm line 1366.
>
> DB:  ERROR ERROR:  pg_atoi: error in "it": can't parse "it"
> not ok (ERROR:  pg_atoi: error in "it": can't parse "it") at test.pl
> line 1453.
> DB:  Row::DESTROY
> DB:  Row::DESTROY
> DB:  FLUSH Recordset id = 12  DBIx::Recordset=HASH(0x1054af98)
> DB:  Disconnect (id=12, numOpen = 1)
> DB:  DESTROY (id=12, numOpen = 1)
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
> For additional commands, e-mail: embperl-help@perl.apache.org

--------------------------------------------------------------
Gerald Richter     ecos electronic communication services gmbh
IT-Securitylösungen * dynamische Webapplikationen * Consulting

Post:       Tulpenstrasse 5          D-55276 Dienheim b. Mainz
E-Mail:     richter@ecos.de          Voice:   +49 6133 939-122
WWW:        http://www.ecos.de/      Fax:     +49 6133 939-333
--------------------------------------------------------------
|
|   ECOS BB-5000 Firewall- und IT-Security Appliance: www.bb-5000.info
|
+-------------------------------------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org


DBIx::Recordset - nonsense query formation

Posted by Terrence Brannon <me...@urth.org>.
Before applying any of the patches that have been emailed to the embperl 
list,
I thought I would first make sure that the test suite passed.

I could not use Angus Lees' "patches" for the test suite because most of 
them
simply skipped the test when $Driver eg 'Pg'.

This is a rather difficult thing to discuss, so I will simply state the 
facts
as I see them and ask questions when appropriate:

[ fact one ]: the recordset docs document what happens when a series of 
fields
is joined by a "|" and prefixed with a "+":

    '+name|text' => 'abc' will expand to name='abc' or text='abc'

[ fact two ]: the docs do _not_ state what happens when the value (e.g. 
"abc"
in the above) is not a simple scalar. However, test.pl and EXAMPLES 
section of
the docs have such a case:

        printlogf "Search \$compconj";
        print LOG "\n--------------------\n" ;

        $set6 -> Search ({"+$t0\lid|$t0\laddon"     =>  "6\tit",
                          "$t0\lname"          =>  'Fourth Name',
                          "\*$t0\lid"           =>  '>',
                          "\*$t0\laddon"        =>  '<>',
                          "\*$t0\lname"         =>  '=',
                          '$compconj'     =>  'and',
                          '$conj'         =>  'or' }) or die "not ok 
($DBI::errstr)" ;


The SELECT query generated by this:

      DB:  'SELECT id, name, txt FROM dbixrs1, dbixrs3 WHERE 
(dbixrs1.value1=dbixrs3.value1) and (  (  (  id > ? and addon <> ?)  or  
(  id > ? and addon <> ?)) or (  (name = ?)))      ' bind_values=<6 6 it 
it Fourth Name> bind_types=<4 1 4 1 1>

does not make sense because the SQL attempts to do this comparison:

    id > it

...that's right, it attempts to compare a numerical field to the string "it"
which rightly yields an error under Postgres.

I'm going to go ahead and fix this, but thought I would report this as
something I perceive as needing to be fixed.

Here is test.log for this particular Search():

Search $compconj...                   
--------------------
DB:  SelectWhere <*addon>=<<>> type = *
DB:  SelectWhere <*id>=<>> type = *
DB:  SelectWhere <+id|addon>=<6    it> type = +
DB:  Composite Field +id|addon
DB:  Composite Field processing id
DB:  Composite Field get   id > ?
DB:  Composite Field processing addon
DB:  Composite Field get   id > ? and addon <> ?
DB:  Key +id|addon gives   (  id > ? and addon <> ?)  or  (  id > ? and 
addon <> ?) bind_values = <6 6 it it> bind_types=<4 1 4 1>
DB:  expr is   (  (  id > ? and addon <> ?)  or  (  id > ? and addon <> ?))
DB:  SelectWhere <$conj>=<or> type = $
DB:  SelectWhere <*name>=<=> type = *
DB:  SelectWhere <name>=<Fourth Name> type = n
DB:  Single Field name
DB:  Single Field gives name = ?
DB:  Key name gives   (name = ?) bind_values = <6 6 it it Fourth Name> 
bind_types=<4 1 4 1 1>
DB:  expr is   (  (  id > ? and addon <> ?)  or  (  id > ? and addon <> 
?)) or (  (name = ?))
DB:  SelectWhere <$compconj>=<and> type = $
DB:  FLUSH Recordset id = 12  DBIx::Recordset=HASH(0x1054af98)
DB:  Row::DESTROY
DB:  Row::DESTROY
DB:  Row::DESTROY
DB:  Row::DESTROY
DB:  Row::DESTROY
DB:  Row::DESTROY
DB:  Row::DESTROY
DB:  Row::DESTROY
DB:  Row::DESTROY
DB:  Row::DESTROY
DB:  Row::DESTROY
DB:  'SELECT id, name, txt FROM dbixrs1, dbixrs3 WHERE 
(dbixrs1.value1=dbixrs3.value1) and (  (  (  id > ? and addon <> ?)  or  
(  id > ? and addon <> ?)) or (  (name = ?)))      ' bind_values=<6 6 it 
it Fourth Name> bind_types=<4 1 4 1 1>
WARN: DBD::Pg::st execute failed: ERROR:  pg_atoi: error in "it": can't 
parse "it" at blib/lib/DBIx/Recordset.pm line 1366.

DB:  ERROR ERROR:  pg_atoi: error in "it": can't parse "it"
not ok (ERROR:  pg_atoi: error in "it": can't parse "it") at test.pl 
line 1453.
DB:  Row::DESTROY
DB:  Row::DESTROY
DB:  FLUSH Recordset id = 12  DBIx::Recordset=HASH(0x1054af98)
DB:  Disconnect (id=12, numOpen = 1)
DB:  DESTROY (id=12, numOpen = 1)



---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org


Re: request for DBIx::Recordset patches

Posted by Kaare Rasmussen <ka...@kakidata.dk>.
> I have never done such extensive patching. I wonder if I could just
> patch the original on a different branch and then pray that I can merge
> them all?

Seems that several of the patches are for the same problem - full qualified 
names contra simple column names. I think you have to pick one.

-- 
Kaare Rasmussen            --Linux, spil,--        Tlf:        3816 2582
Kaki Data                tshirts, merchandize      Fax:        3816 2501
Howitzvej 75               Åben 12.00-18.00        Email: kar@kakidata.dk
2000 Frederiksberg        Lørdag 12.00-16.00       Web:      www.suse.dk


---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org


Re: request for DBIx::Recordset patches

Posted by Terrence Brannon <me...@urth.org>.
Actually, I used the excellent htDig email archives of this list

     http://www.ecos.de/~mailarc/embperl/

and came up with a ream of DBIx::Recordset patches to apply:

http://www.ecos.de/~mailarc/embperl/2002-06/msg00052.html
http://www.ecos.de/~mailarc/embperl/2003-10/msg00025.html
http://www.ecos.de/~mailarc/embperl/2002-02/msg00058.html
http://www.ecos.de/~mailarc/embperl/2002-02/msg00076.html
http://www.ecos.de/~mailarc/embperl/2002-02/msg00063.html
http://www.ecos.de/~mailarc/embperl/2003-05/msg00025.html
http://www.ecos.de/~mailarc/embperl/2003-10/msg00037.html
http://www.ecos.de/~mailarc/embperl/2001-12/msg00090.html
http://www.ecos.de/~mailarc/embperl/2003-10/msg00028.html
http://www.ecos.de/~mailarc/embperl/2001-12/msg00038.html
http://www.ecos.de/~mailarc/embperl/2002-09/msg00114.html
http://www.ecos.de/~mailarc/embperl/2002-01/msg00006.html

I have never done such extensive patching. I wonder if I could just 
patch the original on a different branch and then pray that I can merge 
them all?

I will probably end up doing the whole thing manually, but it's worth 
the ol' college try to get a merge to work.

Off to read the svn docs...

> Tomorrow morning, I will begin applying my patches to the 
> DBIx::Recordset SVN repository in preparation for a new CPAN release. 
> I got svn compiled and running on my Cygwin box, so I am a happy man.
>
> If you have any that you want applied, email them to me with subject 
> header:
>
> [PATCH] DBIx::Recordset
>
> even if the patch is for DBIx::Compat.
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
> For additional commands, e-mail: embperl-help@perl.apache.org
>



---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org


request for DBIx::Recordset patches

Posted by Terrence Brannon <me...@urth.org>.
Tomorrow morning, I will begin applying my patches to the 
DBIx::Recordset SVN repository in preparation for a new CPAN release. I 
got svn compiled and running on my Cygwin box, so I am a happy man.

If you have any that you want applied, email them to me with subject header:

[PATCH] DBIx::Recordset

even if the patch is for DBIx::Compat.





---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org


RE: Embperl CGI and IIS howto

Posted by Maurice McCabe <mm...@orbsoft.com>.
I found 2 methods for debugging ISAPI:
The first one uses a debugger
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore/html
/vcconATLServerAutomaticallyttching.asp

and
the second one uses a trace (webdbg.exe)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore/html
/vcconATLServerViewingTraceMessagesAndHandlingAsserts.asp


If you can send me any mods you made to fastcgi source, I can use that as a
starting point to try to get fastcgi working for embperl on IIS.

Maurice

-----Original Message-----
From: Gerald Richter [mailto:richter@ecos.de]
Sent: Thursday, November 13, 2003 6:03 AM
To: Maurice McCabe
Cc: embperl@perl.apache.org
Subject: Re: Embperl CGI and IIS howto


>
> A long time ago you had the attached correspondence.
>
> I am using isapi_fcgi.dll and it seems to be working for simple test
> scripts, eg, counter.pl. But I need it to work for Embperl.
>
> You mention you got it to work for Embperl after patching the dll. Can you
> send me the dll and any install/config instructions? I can write-up my
> experiences to the list.
>

The problem is that I have only gotten it to run on one computer. The
project for which is needed it, got discared, so didn't done any further
work on it :-( Some times later I have tried on another machine, but didn't
get to work. The probem that you have to put the right values into the
registry and you get no error/debug output, so it's just trial and error.

I think I can dig up the code I have done, but I it will not work, unless
you are able to debug and patch the dll yourself.

Would be really cool to get this working, but I would need a payed project
where I could us it or someone whos pays me for doing so. Anyway if you like
I can look for the sources and send you what I have done so far.

Sorry for bad news

Gerald


---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org


Re: Embperl CGI and IIS howto

Posted by Gerald Richter <ri...@ecos.de>.
>
> A long time ago you had the attached correspondence.
>
> I am using isapi_fcgi.dll and it seems to be working for simple test
> scripts, eg, counter.pl. But I need it to work for Embperl.
>
> You mention you got it to work for Embperl after patching the dll. Can you
> send me the dll and any install/config instructions? I can write-up my
> experiences to the list.
>

The problem is that I have only gotten it to run on one computer. The
project for which is needed it, got discared, so didn't done any further
work on it :-( Some times later I have tried on another machine, but didn't
get to work. The probem that you have to put the right values into the
registry and you get no error/debug output, so it's just trial and error.

I think I can dig up the code I have done, but I it will not work, unless
you are able to debug and patch the dll yourself.

Would be really cool to get this working, but I would need a payed project
where I could us it or someone whos pays me for doing so. Anyway if you like
I can look for the sources and send you what I have done so far.

Sorry for bad news

Gerald


---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org


Re: Embperl CGI and IIS howto

Posted by Maurice McCabe <mm...@orbsoft.com>.
Gerald,

A long time ago you had the attached correspondence.

I am using isapi_fcgi.dll and it seems to be working for simple test
scripts, eg, counter.pl. But I need it to work for Embperl.

You mention you got it to work for Embperl after patching the dll. Can you
send me the dll and any install/config instructions? I can write-up my
experiences to the list.

Thanks,

Maurice


> PerlEx -
> after installation....
> I changed the file association for .epl from
>
> C:\perl\bin\perl.exe c:\mysite\embpcgi.pl %s
>
> to
>
> C:\perl\bin\PerlISEX.dll  c:\mysite\embpcgi.pl %s
>
> ...but no luck there - is this vaguely right - any ideas?

Perlex is not good for this, you can use perlis.dll, but this also doesn't
accept an argument, so it won't work this way. I have developed an IIS
filter dll, that make it possible to use it, but at the moment there are
some issues with threads and Perl memory management, so it isn't usabe right
now.

> FastCGI -
> after installing FCGI, I changed the associations from:
>
> C:\perl\bin\perl.exe c:\mysite\embpcgi.pl %s
>
> to
>
> C:\perl\bin\perl.exe c:\mysite\embpfastcgi.pl %s
>
> ...which didn't break anything - but didn't seem to give me a performance
> increase - am I missing something here too ?

It will things a little bit slower, because it additional loads FCGI.pm, but
for the rest it's just doing the same.

FastCGI is working different, you need a dll that dispatchs the request to
an extra process. There is one called isapi_fcgi.dll (see www.fastcgi.com
for the source), but I had to patch it to get it working with Perl/Embperl
(the author uses it for PHP). I have done this last week and it seems to
work fine. The main problem is, that it has no diagnostics and you have to
set sveral registry keys to get it working. On a computer without a Visual
C++ Debugger, you can't see what going wrong. I like to add some logging
function and then I will publish the way how to use it...

...and then things really runing much faster, then with a normal CGI

Gerald


-------------------------------------------------------------
Gerald Richter    ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting

Post:       Tulpenstrasse 5         D-55276 Dienheim b. Mainz
E-Mail:     richter@ecos.de         Voice:    +49 6133 925131
WWW:        http://www.ecos.de      Fax:      +49 6133 925152
-------------------------------------------------------------



---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org


Re: DBIx::Recordset status

Posted by Gerald Richter <ri...@ecos.de>.
Hi,

it's true DBIx::Recordset hasn't been updated for a long time. The reason is
simple, it does all I need :-) Anyway I have a set of patches people send me
and it would be worth putting them into a new release. Also there are some
ideas what can be enhanced. As you already know I don't have the time to do
it right now and when I have time I like to put it into Embperl to get 2.0
finaly done.

So maybe somebodyelse could help in maintaining DBIx::Recordset (or take
over the maintainance). I can setup a public CVS (or better svn) which holds
the sources, so it should be quite easy to cooperate.

I think the work Angus has already done for the Debian release is a good
starting point. Also the docs Terrence has written should be considered to
be included

Anybody likes to give it a try?

Gerald


Angus Lees wrote:
> At Thu, 2 Oct 2003 17:41:36 -0700, Terrence Brannon wrote:
>> The Perl object-oriented Persistence group
>> (poop-group@sourceforge.net), has
>> stated that their list of reviewed modules will drop DBIx::Recordset
>> within
>> six months unless it appears that the module is being maintained
>> (ie, new
>> releases are made).
>
> <aside>
>
> I find it interesting that they only consider code worthwhile if its
> not finished yet..
>
> I really don't get this "newer is better" philosophy that is so
> prevalent in new-age computing circles.  From what I can see, "being
> new" is a point *against* the quality of a piece of code.
>
> </aside>
>
>> But they were wondering if a new release were coming out or if there
>> were
>> any outstanding bugfixes/features to be done to the code.
>
> I've accumulated quite a few bugfixes from various sources.  I
> seriously recommend anyone distributing DBIx::Recordset look over
> them, they should be trivial to separate from the Debian-specific
> packaging parts:
>
>
http://ftp.debian.org/debian/pool/main/libd/libdbix-recordset-perl/libdbix-recordset-perl_0.24-7.diff.gz
>
> The debian/changelog file (and http://bugs.debian.org/<number> where a
> bug number is given) should give details about each patch where its
> purpose isn't already obvious.

--------------------------------------------------------------
Gerald Richter     ecos electronic communication services gmbh
IT-Securitylösungen * dynamische Webapplikationen * Consulting

Post:       Tulpenstrasse 5          D-55276 Dienheim b. Mainz
E-Mail:     richter@ecos.de          Voice:   +49 6133 939-122
WWW:        http://www.ecos.de/      Fax:     +49 6133 939-333
--------------------------------------------------------------
|
|   ECOS BB-5000 Firewall- und IT-Security Appliance: www.bb-5000.info
|
+-------------------------------------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org


Re: DBIx::Recordset status

Posted by Angus Lees <gu...@debian.org>.
At Thu, 2 Oct 2003 17:41:36 -0700, Terrence Brannon wrote:
> The Perl object-oriented Persistence group (poop-group@sourceforge.net), has
> stated that their list of reviewed modules will drop DBIx::Recordset within
> six months unless it appears that the module is being maintained (ie, new
> releases are made).

<aside>

I find it interesting that they only consider code worthwhile if its
not finished yet..

I really don't get this "newer is better" philosophy that is so
prevalent in new-age computing circles.  From what I can see, "being
new" is a point *against* the quality of a piece of code.

</aside>

> But they were wondering if a new release were coming out or if there were
> any outstanding bugfixes/features to be done to the code.

I've accumulated quite a few bugfixes from various sources.  I
seriously recommend anyone distributing DBIx::Recordset look over
them, they should be trivial to separate from the Debian-specific
packaging parts:

 http://ftp.debian.org/debian/pool/main/libd/libdbix-recordset-perl/libdbix-recordset-perl_0.24-7.diff.gz

The debian/changelog file (and http://bugs.debian.org/<number> where a
bug number is given) should give details about each patch where its
purpose isn't already obvious.

-- 
 - Gus


---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org


Re: DBIx::Recordset status

Posted by Robert <ro...@robert.cz>.
Kee Hinckley wrote:

>> Isn't there such a thing as - Hey it just works and is good enough
>
>
> That was certainly my thought.  I use it heavily on all my sites. 
> There are some things we've discussed on this list that might be nice 
> (bigint support), but generally it does what I want.

Yes, it does. Gerald, please, mark it version 1.0 and everybody will be 
happy ;-)

- R.


---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org


Re: DBIx::Recordset status

Posted by Kee Hinckley <na...@somewhere.com>.
At 12:26 AM -0400 10/3/03, Ruben Safir Secretary NYLXS wrote:
>Isn't there such a thing as - Hey it just works and is good enough

That was certainly my thought.  I use it heavily on all my sites. 
There are some things we've discussed on this list that might be nice 
(bigint support), but generally it does what I want.
-- 
Kee Hinckley
http://www.messagefire.com/         Next Generation Spam Defense
http://commons.somewhere.com/buzz/  Writings on Technology and Society

I'm not sure which upsets me more: that people are so unwilling to accept
responsibility for their own actions, or that they are so eager to regulate
everyone else's.

---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org


Re: DBIx::Recordset status

Posted by Ruben Safir Secretary NYLXS <ru...@mrbrklyn.com>.
Isn't there such a thing as - Hey it just works and is good enough

Ruben

On Thu, Oct 02, 2003 at 05:41:36PM -0700, Terrence Brannon wrote:
> The Perl object-oriented Persistence group (poop-group@sourceforge.net), has
> stated that their list of reviewed modules will drop DBIx::Recordset within
> six months unless it appears that the module is being maintained (ie, new
> releases are made).
> 
> I told them that I am creating a set of docs for Recordset which include
> running code samples for every aspect of Recordset:
> 
> 
> http://theoryx5.uwinnipeg.ca/CPAN/data/DBIx-Recordset-Playground/Playground.
> html
> 
> Which is based on a fairly comprehensive sample database schema:
> 
> 
> http://theoryx5.uwinnipeg.ca/CPAN/data/DBSchema-Sample/DBSChema/Sample.html
> 
> 
> But they were wondering if a new release were coming out or if there were
> any outstanding bugfixes/features to be done to the code.
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
> For additional commands, e-mail: embperl-help@perl.apache.org

-- 
__________________________
Brooklyn Linux Solutions
__________________________
DRM is THEFT - We are the STAKEHOLDERS http://fairuse.nylxs.com

http://www.mrbrklyn.com - Consulting
http://www.inns.net <-- Happy Clients
http://www.nylxs.com - Leadership Development in Free Software
http://www2.mrbrklyn.com/resources - Unpublished Archive or stories and articles from around the net
http://www2.mrbrklyn.com/downtown.html - See the New Downtown Brooklyn....

1-718-382-0585

---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org


DBIx::Recordset status

Posted by Terrence Brannon <tb...@directsynergy.com>.
The Perl object-oriented Persistence group (poop-group@sourceforge.net), has
stated that their list of reviewed modules will drop DBIx::Recordset within
six months unless it appears that the module is being maintained (ie, new
releases are made).

I told them that I am creating a set of docs for Recordset which include
running code samples for every aspect of Recordset:


http://theoryx5.uwinnipeg.ca/CPAN/data/DBIx-Recordset-Playground/Playground.
html

Which is based on a fairly comprehensive sample database schema:


http://theoryx5.uwinnipeg.ca/CPAN/data/DBSchema-Sample/DBSChema/Sample.html


But they were wondering if a new release were coming out or if there were
any outstanding bugfixes/features to be done to the code.




---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org


Re: A TABLE-processing-with-[$ while $]-blocks-involved question

Posted by Gerald Richter <ri...@ecos.de>.
> The postgres log reported the following for the rsmbacontracts query:
>
> LOG:  query: SELECT * FROM clientcontracts WHERE accountguid =
> 'b6ea9cafe2d1997392d166b96e5697b1';
> LOG:  pq_recvbuf: unexpected EOF on client connection
>

THe only reason I can image is that Embperl segfaults because of the
inproper nesting, instead of gving an error message like it should.

Which version of Embperl?

Do you see anything in the error log when this happens?

Gerald



--------------------------------------------------------------
Gerald Richter     ecos electronic communication services gmbh
IT-Securitylösungen * dynamische Webapplikationen * Consulting

Post:       Tulpenstrasse 5          D-55276 Dienheim b. Mainz
E-Mail:     richter@ecos.de          Voice:   +49 6133 939-122
WWW:        http://www.ecos.de/      Fax:     +49 6133 939-333
--------------------------------------------------------------
|
|   ECOS BB-5000 Firewall- und IT-Security Appliance: www.bb-5000.info
|
+-------------------------------------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org
For additional commands, e-mail: embperl-help@perl.apache.org