bcp patches (was: Re: 0.91RC1)

Frediano Ziglio <[email protected]>
Newsgroups gmane.comp.db.tds.freetds
Message-ID <[email protected]>
Hi,
  personally I don't like environment, I prefer stdin as suggested or
kerberos when possible.

About hints you are right but I don't think patch is correct. First a
strndup should be used will all cascading code (mainly free in the
right places!). What happen also if anybody wants to set multiple
hints ?? I looked at code and seems that hint goes directly to insert
bulk statement so it would be possible to set a string like
"TABLOCK,ROWS_PER_BATCH=100" but why checking partially string and
then accept the entire string with any options?

Frediano

2011/4/10 Konrad J Hambrick <[email protected]>:
>
> James / Freddy / Bill --
>
> I hope I am not too late ...
>
> I submitted a patch long ago against version 0.64
> to fix those Hints that require info in addition
> to the hint keyword itself( ORDER, ROWS_PER_BATCH
> and KILOBYTES_PER_BATCH ) ...
>
> Anyhow, the fix seems to have gotten lost somewhere ...
>
> See attached patch against src/dblibs/bcp.c:
>
>   src-dblib-bcp.c-diff-u-kjh.patch
>
> I also found it useful (and more secure ps-wise) to
> avoid setting the HostName / UserName / PassWord on
> the commandline.
>
> freebcp.c already looks for a environment varb: FREEBCP
> so I added code to src/apps/freebcp.c to use FREEBCPHOST,
> FREEBCPUSER and FREEBCPPASS from the user's environment
> instead of from the commandline.
>
> See attached src-apps-freebcp.c-diff-u-kjh.patch ...
>
> Thanks for FreeTDS !
>
> -- kjh
>
>
> James K. Lowden wrote, On 04/09/2011 03:33 PM:
>>
>>
>> http://www.ibiblio.org/pub/Linux/ALPHA/freetds/stable/release_candidates/freetds-0.91rc1.tgz
>>
>> FreeTDS proudly, and with great relief, announces the first release
>> candidate for its next version, 0.91.  It will supersede the current
>> version, 0.82, released in May 2008.
>>
>> The jump in release numbers represents three years' progress.  We issue
>> releases infrequently to minimize users' administrative overhead.  But
>> the time has truly arrived to raise the flag and tell everyone to
>> upgrade.
>>
>> Please give it a whirl.
>>
>> As a member of this mailing list, your feedback is invaluable both to
>> the developers and to the larger FreeTDS community. (That community
>> very likely numbers in the tens of thousands, btw.)  Any problems you
>> discover with a release candidate is one that can be avoided in the
>> actual release.  This is your chance to make a difference.
>>
>> In particular, we need to know about things we devlopers don't deal with
>> ourselves, i.e.:
>>
>> 1.  Proprietary OSes, big iron and small.
>> 2.  Other language bindings, from DBI to PHP and beyond.
>> 3.  Behavior changes versus 0.82 that necessitate administrative or
>> programming changes.
>>
>> Notable new features, in reverse chronological order:
>>
>> 1.  Full Kerberos and SSPI support for passwordless login to
>> Microsoft SQL Server from Unix and Windows clients.  Includes Keberos
>> delegation option.
>>
>> 2.  Full support for DB-Library under Win32/64 via NMAKE.EXE.
>>
>> 3.  Built-in support for UTF-8.
>>
>> 4.  Support for wide characters in ODBC.
>>
>> 5.  Support for varchar(max) and varbinary(max).
>>
>> 6.  Better thread-safety in ODBC.
>>
>> 7.  Error messages distinguish between connect and login errors.
>>
>> 8.  Bulk-copy functions in CT-Library.
>>
>> 9.  Correct handling of query timeouts and cancellations.
>>
>> Your humble maintainer,
>>
>> --jkl
>>
>>
>> _______________________________________________
>> FreeTDS mailing list
>> [email protected]
>> http://lists.ibiblio.org/mailman/listinfo/freetds
>>
>
> _______________________________________________
> FreeTDS mailing list
> [email protected]
> http://lists.ibiblio.org/mailman/listinfo/freetds
>
>
_______________________________________________
FreeTDS mailing list
[email protected]
http://lists.ibiblio.org/mailman/listinfo/freetds
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.