Re: [python-sybase] Problems invoking stored procedures

[Marcos P. <msa...@gr...>]

VB seems to store these in a connection-level variable and/or associate
callback/event procedures. It might be a good solution, especially for
warnings and informative messages.

El vie, 29-11-2002 a las 06:00, Dave Cole escribi=F3:
> >>>>> "hopfgartner" =3D=3D hopfgartner  <hop...@ro...> writes:
>=20
> >> You don't say whether or not you are using FreeTDS.  I also get
> >> segfaults in FreeTDS 0.60 when I try to call stored procedures.  I
> >> have not tried the current CVS version of FreeTDS.  Something to
> >> try a bit later.
> >>=20
> hopfgartner> Sorry, I've forgot to mention it. Indeed, I'm using
> hopfgartner> FreeTDS 0.6.
>=20
> That helps a bit.
>=20
> >> Is it an error to have the stored procedure error message reported
> >> as an exception?
> >>=20
> hopfgartner> This should not be an error from the SQL server, but I
> hopfgartner> will look closer to it. This is simply a message telling
> hopfgartner> that there are no FK referencing this table. When running
> hopfgartner> from Query Analyser, this message appears in the
> hopfgartner> 'Messages' tab, wheras results are in the 'Grid' tab.
>=20
> That raises the question of what I should do with messages from the
> stored procedure.  Should I simply discard the messages?
>=20
> hopfgartner> The same stored procedure does not give any error
> hopfgartner> messages when run from Query Analyser.
>=20
> It would be really helpful if you could send a fragment of SQL (no
> matter how trivial) that I could run here to set up the exactly same
> situation that you are seeing.
>=20
> - Dave
--=20
Marcos S=E1nchez Provencio <msa...@gr...>
www.burke.es