On Fri, Sep 17, 2004 at 03:25:41PM -0400, Jeff Urlwin <[EMAIL PROTECTED]> wrote:
> >
> >
> > What happens, is that the backup proceeds
> > normally until just before it finishes. Then, the backup
> > file (which I have watched grow during execution) is removed
> > and the command finishes wit
Thanks to Peter Scott for being the first to reply.
Just to make clear, the module I'm asking to have named today is just
a container that defines actions which can be done against a
database, but it does not actually talk to any databases or otherwise
execute the definitions.
Therefore, "[dbms
At 12:04 AM 9/18/2004, Darren Duncan wrote:
The main reason concerns a revisiting of one of the module's main
intended uses, which was to support the idea of any database-related
activity being representable by a SQL routine or imitation thereof. An
implementation of a SQL routine that my module
DBD::Teradata 1.20 is now available on CPAN.
Changes:
- added encrypted logon support
- removed non-SQL connection support
- revised/clarified license text
Note that this is a "lite" version of the
feature rich, actively maintained version
described at
http://www.presicient.com/tdatdbd.
Be sure to
I need to access MS SQL server from CGI scripts running on Linux box.
Here in Russia we have a pain using 2 different
charsets for Cyrillic: CP1251 on Windows and KOI8-R on Unices.
So all the data bases on MS SQL server have data in CP1251,
but CGI scripts use KOI8-R.
Transferring data from SQL s
This is a request for comment with the intent of determining a better
name for one of my CPAN modules prior to it being registered with the
Perl 5 Module List. The module in question has been using the name
"SQL::SyntaxModel" since about September 26th of 2003, following a
previous RFC process
