ition. I can't teach you all there is to know about SQL 7's
system catalogues, but you have everything you need in sysobjects, and
syscolumns, and sysindexes (although I usually use sp_helpindex to bring in
information to create indexes on the fly). From there, it's really up to you
ho
ou get the hang of
using this, you can easily get the other properties listed in perldoc DBI.
Hope this helps,
Steve H.
-Original Message-
From: eric wang [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 05, 2001 2:58 PM
To: dave hoover; Eric Wang; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED
ilto:[EMAIL PROTECTED]]
> Sent: Thursday, July 05, 2001 12:43 PM
> To: Eric Wang; [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: creating columns on the fly
>
>
> Eric Wang wrote:
> [snip]
> > First, I decided that I will need to generate the
> > S
on the fly
Eric Wang wrote:
[snip]
> First, I decided that I will need to generate the
> SQL statements inside
> the perl script. (i.e. print SQL "insert...
> blah..").
If you use DBI, this is no problem, in fact, it's
expected. You will probably call
$sth->execu
Eric Wang wrote:
[snip]
> First, I decided that I will need to generate the
> SQL statements inside
> the perl script. (i.e. print SQL "insert...
> blah..").
If you use DBI, this is no problem, in fact, it's
expected. You will probably call
$sth->execute(SQL_HERE). You can plug in a previousl
Hi guys,
I am writing a perl script that will take some command prompt parameters
and linking it with a SQL server database. I sort of have an idea on how
to do it. But need you guys to give me some directions as to which way
is the best.
First, I decided that I will need to generate the SQL s
