[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Sheflug] sybase, anyone?
On Tue, 2002-05-14 at 17:33, stephen.tozer-loft [at] sth.nhs.uk wrote:
> The sybase database is part of a 3rd party product. As such, the
> manufacturers only let us mess with their database by using their own
> Special Procedures (a Sybase technical term).
Stored Procedures, shurely?
> So we have to call the SPs, which rules out bcp I think, and possibly some
> of your other ideas (?).
You can access Sybase stored procedures via any open access client
(isql, for example). The authorisation mechanism will be via
username/password access, and that will be what is limiting your access
to actual tables. Any standard software which can talk Sybase/MSSQL will
be able to connect to it. Stored procedures are standard Transact-SQL.
> language. I know a bit about SybPerl, but suspect it won't help with my
> specific problem....with me so far?....
DBD::Sybase (http://search.cpan.org/doc/MEWP/DBD-Sybase-0.94/Sybase.pm)
will work. Either use debian (apt-get install libdbd-sybase-perl ;) or
setup CPAN (perl -MCPAN -e 'install DBD::Sybase').
> Even more specifically, these timestamp things seem to be binary numbers,
All numbers in computers are binary at some stage :)
> and I'm not sure exactly how to handle them within C. However I declare
> them, the 'put' SP calls don't accept the update.
Show us the data, might be able to help. Probably just a standard SQL
Datetime, possibly an inserted Unix date or sommink.
> If anyone's still with me, I could show them some code to shed a bit more
> light.
Code! Code! Code! (etc.)
:)
Cheers,
Alex.
___________________________________________________________________
Sheffield Linux User's Group -
http://www.sheflug.co.uk/mailfaq.html
GNU the choice of a complete generation.