Re: DBD::mysql
[EMAIL PROTECTED] (Rudy Lippan) writes: From the ChangeLog: * Fixed bug where strings that were used in numeric context were not getting quoted on execute(). Now all parameters are bound as varchar by default. **NOTE** this is a change in behaviour that MAY cause problems with some SQL statements. If quoted integers, for example, cause any problems, use bind_param(column_id, SQL_INTEGER) to force a column to be bound as an integer. And the thread: http://www.mail-archive.com/[EMAIL PROTECTED]/msg02133.html Why not use SQL_INTEGER by default if /^\d+$/? The database will convert the integer to a string if needed. --Bill. -- William R Ward[EMAIL PROTECTED] http://www.wards.net/~bill/ - PROFESSIONAL PROGRAMMER, CLOSED COURSE. DO NOT ATTEMPT.
Re: RFC Params::Normalize
[EMAIL PROTECTED] (Michel Rodriguez) writes: Variable/Parameter conventions can start religious wars, so I would like to offer module authors a way to be a little oecumenical, so they can easily offer named parameters that follow the one_true_perl_convention or even the baddlyNamedCamelCaseConvention. Very cool idea. Have you considered using a tied hash interface for this? I think that would be very slick... --Bill. -- William R Ward[EMAIL PROTECTED] http://www.wards.net/~bill/ - A foolish consistency is the hobgoblin of little minds, adored by little statesmen and philosophers and divines.- Emerson
Re: Pod::DocBook
[EMAIL PROTECTED] (Christopher Hicks) writes: On Mon, 9 Jun 2003, Shlomi Fish wrote: Last I saw him, he was muttering I think not... at a party. Haven't seen him since. When was that exactly? A Renee Descartes joke. Randal is a very funny guy. Remember I think therefore I am well the corollary is I think not therefore I am not which leads to several versions of Descartes philosophically humorous demise. It's the single most popular philosophy joke in my experience. The only philosophy class I took in college was Logic. And there I learned that you are wrong. I think, therefore I am does not imply I think not, therefore I am not. It does, however, imply I am not, therefore I think not (and vice-versa). This is called modus tollens and you can read more about it from Wikipedia, the open-source encyclopedia: http://www.wikipedia.org/wiki/Modus_tollens --Bill. -- William R Ward[EMAIL PROTECTED] http://www.wards.net/~bill/ - A foolish consistency is the hobgoblin of little minds, adored by little statesmen and philosophers and divines.- Emerson
Re: UDPM name space finalization
One quick comment - why not follow DBI's lead and use ::PurePerl:: instead of ::Perl::? --Bill. -- William R Ward[EMAIL PROTECTED] http://www.wards.net/~bill/ - A foolish consistency is the hobgoblin of little minds, adored by little statesmen and philosophers and divines.- Emerson
Re: RFC Text::UberText
Chris Josephes writes: On 15 Oct 2002, William R Ward wrote: For me, it's because TT allows Perl to be embedded in the template. That way lies madness. The advantage of a templating system is that you can leave the template maintenance to someone who doesn't know programming, and let the programmer focus on the logic. If logic gets mixed in with markup, then you might as well not be using here documents. TT allows Perl to be embedded in a template (through the [% perl %] block, but doesn't necessarily mandate it or rely on it like other systems. Text::UberText could just as easily have a module created that allowed for perl code inclusion, and someone could easily write one for HTML::Template. It's too much of a temptation to allow for Perl code inclusion, in my book. People tend to take shortcuts if they're given. I think that debate has been covered well in the O'Reilly Network article that Leon Brocard mentioned earlier in the thread (http://www.perl.com/pub/a/2001/08/21/templating.html) I haven't seen that yet, I'll give it a read... I'm not a fan of inline code myself, but I don't want to restrict users either. It's not my desire to keep someone from shooting themselves in the foot. I don't want to restrict Perl programmers. I want to restrict the number of things that an HTML designer has to know to update the template. The one argument I will make against inline code is that is limits the template application to the perl language. HTML::Template has a parser written in Java, and it's not inconceivable that TT or UT could have parsers written in Java or Python sometime down the road. That was one of the reasons I didn't want perl syntax creeping into the UT grammar. That's another good reason... --Bill. -- William R Ward[EMAIL PROTECTED] http://www.wards.net/~bill/ - Consistency is not really a human trait. --Maude (from the film Harold Maude)
Re: RFC Text::UberText
[EMAIL PROTECTED] (Chris Josephes) writes: SYNOPSIS I've been working on a set of modules for a couple of weeks now based on work I've been doing with several web page authors and copywriters. I created a module named Text::UberText which is designed to be a lightweight template system with the ability to be extended easily with third party code. [...] OTHER TEMPLATE PARSERS [...] You overlooked HTML::Template, which I think would meet all of your needs. It is unfortunately buried under HTML:: but it is useful for all kinds of templating tasks. Anyway, rather than creating a new syntax, why not submit patches to some existing templating system to add the features you want? What do you mean by uber? Do you mean über? If so, to avoid the ü charadcter, it should be ueber instead... --Bill. -- William R Ward[EMAIL PROTECTED] http://www.wards.net/~bill/ - Consistency is not really a human trait. --Maude (from the film Harold Maude)
Naming help - WWW::UserDB
I'm working on a module that will handle the implementation of a login/password system for a CGI-based or mod_perl-based application. It doesn't use the HTTP authentication scheme, but instead has the kind of scheme we've all grown used to seeing at various e-commerce and similar sites, where you log in via a form on the web page, and there's a mechanism to update your info, change your password, etc., and if you forget your password it will handle that situation as well. It uses MD5 to encrypt the passwords and for a session cookie, and DBI to access a database. The fields are all configurable. But what to call it? For now I've been using the name "WWW::UserDB" but I'm not sure that's the best name. Any other suggestions/ideas? --Bill. -- William R Ward[EMAIL PROTECTED] http://www.bayview.com/~hermit/ - If you're not part of the solution, you're part of the precipitate.
