Hello,
As you see below, I'm quite desperate. Can someone help me fix the
Devel::CallerItem and Devel::DumpStack modules on CPAN? They have no
Makefile.PL and because of that it is difficult to install them.
I attach here the same modules WITH Makefile.PL. Obviously, I cannot change
the modules themselves as I'm not the author of those modules, and the
author is un-reachable for quite a long time.
PLEASE! I get many requests from user of my module Log::LogLite, about this
problem, and this is the second request about it to [EMAIL PROTECTED]
Thanks in advance,
Rani
-----Original Message-----
From: Terrence Brannon [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 25, 2001 4:21 PM
To: Rani Pinchuk
Subject: Re: SQL::Catalog - test, label, store, search and retrieve SQL
queries
On Thursday, October 25, 2001, at 07:01 AM, Rani Pinchuk wrote:
> Thanks Terrence for referencing my module.
>
> Yet, I would like to know why you find installing Log::Lite difficult.
> Is it
> the Devel::CallerItem and Devel::DumpStack modules?
yeah, the old ones my Jack Shirazi where hell to install... heheh... but
I think Dave Rolsky has a newer Devel::Dumpstack which is easy to
install.
> I ask because if this is the reason, I will just forward your answer to
> CPAN
> people, asking them again to fix those two modules (those modules comes
> without Makefile.PL which makes it difficult to install. It is easy to
> fix,
> yet as I'm not the author of those modules, I cannot change them on
> CPAN).
>
> Thanks again,
>
> Rani
>
> -----Original Message-----
> From: Terrence Brannon [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, October 25, 2001 3:49 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: ANN: SQL::Catalog - test, label, store, search and retrieve SQL
> queries
>
>
> The URL
>
>
> http://princepawn.perlmonk.org/domains/semantic-
> elements.com/cpan/SQL-Catalog-0.01.tar.gz
>
> has entered CPAN as
>
> file: $CPAN/authors/id/T/TB/TBONE/SQL-Catalog-0.01.tar.gz
>
> NAME
> SQL::Catalog - test, label, store, search and retrieve SQL queries
>
> SYNOPSIS
> shell% cd sql_lair/city,date/weather/1/
>
> shell% cat concrete.sql
> select city, date from weather where temp_lo < 20;
> shell% sql_test concrete.sql
> shell% cat testexec.out # see results of prepare, execute on this
>
> shell% cat abstract.sql
> select city, date from weather where temp_lo < ?;
> shell% sql_test abstract.sql 55 # send in placeholder value
> shell% cat testexec.out # to see results... looks good
>
> shell% sql_register abstract.sql basic_weather
> [hi_and_low] inserted as
> [select city from weather where temp_lo > ? and temp_hi > ? LIMIT
> 10]
>
> ... then in a Perl program (e.g. test.pl in this distribution)
> my $dbh = SQL::Catalog->db_handle; # optional - get the handle as
> you please
> my $sql = SQL::Catalog->lookup('hi_and_low');
> my $sth = $dbh->prepare($sql);
> $sth->execute(55);
>
> my $rows = $sth->rows;
>
> DESCRIPTION
> Over time, it has become obvious that a few things about SQL
> queries
> are
> necessary. One, you want to be able to get a query by a label. Two,
> you
> want to be able to look through old queries to see if someone else
> has
> written one similar to what you want. Three, you want the database
> guru
> to develop queries on his own and be able to register them for your
> use
> without interfering with him. Four, you want to be able to answer
> questions such as "what queries are doing a select on such-and-such
> tables".
>
> Well, wait no longer, for your solution has arrived.
>
> COMMON STEPS TO USAGE
> Develop your concrete query in a db shell
>
> The first step to developing a database query is to play around at
> the
> db shell. In this case, you normally dont have any placeheld
> values.
> You
> just keep mucking with the query until it gives you what you want.
>
> When you finally get what you want, save it in a file, say
> `concrete.sql' for example. Here is a concrete query:
>
> select city, date from weather where temp_hi > 20
>
> Abstract your query with placeholders
>
> Now it's time to make your query more abstract. So we do the
> following:
>
> select city, date from weather where temp_hi > ?
>
> and save in a different file, say `abstract.sql'.
>
> But let's test this query next:
>
> sql_test abstract.sql 34
>
> And let's cat testexec.out to see the results.
>
> Register your query
>
> sql_register abstract.sql city_date_via_temp_hi
>
> and the system tells you
>
> [city_date_via_temp_hi] saved as
> [select city, date from weather where temp_hi > ?]
>
> Use your query from DBI:
>
> use SQL::Catalog;
>
> my $dbh = SQL::Catalog->db_handle;
> my $SQL = SQL::Catalog->lookup('city_date_via_temp_hi') or die
> "not
> found";
> my $sth = $dbh->prepare($SQL, $cgi->param('degrees'));
> .... etc
>
> What you must do
> * edit sub db_handle so it gets a database handle.
> * copy the sql_* scripts to a place on your `$PATH'
> * create a table named sql_catalog. a script for Postgresql is
> provided.
> What SQL::Catalog does
> It stores each query in a database table. I could have gone for
> something more fancy in database design but wanted to maintain
> database
> independence without requiring extra tools for schema creation and
> database use.
>
> The queries are stored in this table:
>
> CREATE TABLE sql_catalog (
> query varchar(65535) , # the actual query
> tables varchar(255) , # tables used
> columns varchar(255) , # fields selected
> cmd varchar(40) , # SELECT, INSERT, UPDATE, etc
> phold int4 # number of bind_values
> );
>
> Query field omitted for brevity. It has (wouldya guess) the SQL
> query.
>
> mydb=# select label,cmd,columns,tables,phold from sql_catalog;
> label | cmd | columns |
> tables | phold
>
> ---------------+--------+-------------------------------------------------
--
> weather_hi | SELECT | weather.city,weather.date |
> weather | 1
> hi_and_low | SELECT | weather.city |
> weather | 2
>
> AUTHOR
> T. M. Brannon, <[EMAIL PROTECTED]>
>
> SEE ALSO
> * Class::Phrasebook::SQL performs a similar function. It
> stores a "phrasebook" of SQL in XML files. It has some rather
> daunting
> satellite module requirements to get the non-optional the Log::Lite
> manpage to work.
> * DBIx::SearchProfiles does query labeling and also has some
> convenience functions for query retrieval. It does not store the
> SQL
> in
> a database or make it searchable by table, column, or number of
> placeholders.
>
Fwd: Fwd: Log::LogLite requires Devel::DumpStack?
From: Rani Pinchuk <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Date: Mon, 02 Jul 2001 20:50:29 GMT
Message-ID: <[EMAIL PROTECTED]>
Hello,
Can someone please help me with this? The email of Jack Shirazi is no
longer valid. Can someone update his modules? I attached the "fixes" that
are needed (namely - a usual package with Makefile.PL, test.pl etc...).
Thanks,
Rani
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 7/3/01, 12:39:57 AM, Rani Pinchuk <[EMAIL PROTECTED]> wrote regarding Fwd:
Log::Loglite requires Devel::DumpStack?:
> Hello Jack,
> I was wondering if you still support the modules Devel::DumpStack and
> Devel::CallerItem. I looked at you directory and saw that the files there
> are from 1995.
> The reason I ask is that I wrote a class that uses those modules. I found
> your modules extremely useful and was quite shocked to find out that you
> wrote them so long ago (around the time I started to learn Perl). Yet -
> because the modules are supplied without Makefile.PL, it is not obvious
> how to install them (as you see below).
> I attached to this email your modules as tar.gz files with the
> Makefile.PL files and the rest of the usual parts in a CPAN package, so
> they can be installed easily. I wonder if you mind to upload those.
> I will appreciate any comment from you (even if it is a simple "no").
> Anyway, thanks in advance,
> Rani
> >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
> On 7/2/01, 6:43:14 PM, Michael Dube wrote regarding
> Log::Loglite requires Devel::DumpStack?:
> > Hi,
> > I am trying to install Log::Loglite on Solaris 2.7. I installed the
> prereq
> > of IO::LockedFile, but 'make test' still complains that it can't find
> > Devel::DumpStack. I found this module on CPAN, but it is only a .pm
> file,
> > with no installation instruction. I put it in my module path, and the
> 'make
> > test' seems to find it, but then it complains about 'Can't locate
> > auto/Devel/DumpStack/autosplit.ix'. Do you know anything about this?
> > Mike
Devel-CallerItem-0.10.tar.gz
Devel-DumpStack-0.10.tar.gz
