|
Archives of the TeradataForumMessage Posted: Thu, 15 Jul 2004 @ 07:12:14 GMT
My local perl hacker informs me that the current version of TeraPerl does not understand password encryption at V2R5.1 and beyond. Because TeraPerl is standalone (only perl needed), I suspect that the problem is that the package has implemented the underlying TCP/CLIv2 protocols internally and the old protocols did not include encryption. If enhanced it's likely to be a for-cost upgrade because the developer, a former student, is now working for a living. The workaround, and possible future direction for Teradata and perl, appears to be the perl ODBC interface also from CPAN (I think - I'm not a perl user). With the ODBC interface, the perl DBD connects to the Teradata via the standard Teradata ODBC driver, which allows the driver to isolate perl from the messy interface details. /dave "nawk" hough
| ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||