I'd like to suggest the implementation and use of an Exception class for
error handling, very much like Java and dotNET have. Being able to throw
anything in case of an error is nice. But having a default wrapper class
makes accessing this information easier and more generic. What do you think?
__________________________________________________________
Deze e-mail en de inhoud is vertrouwelijk en uitsluitend bestemd voor de geadresseerde(n). Indien u niet de geadresseerde bent van deze e-…
[View More]mail verzoeken wij u dit direct door te geven aan de verzender door middel van een reply e-mail en de ontvangen e-mail uit uw systemen te verwijderen. Als u geen geadresseerde bent, is het niet toegestaan om kennis te nemen van de inhoud, deze te kopieren, te verspreiden, bekend te maken aan derden noch anderszins te gebruiken.
The information contained in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Please notify us immediately if you have received it in error by reply e-mail and then delete this message from your system.
__________________________________________________________
[View Less]
Anybody with a Alpha around to test this?
http://buildd.debian.org/fetch.cgi?&pkg=pike7.6&ver=7.6.112-1&arch=alpha&st…
I saw a discusion about this maybe being libjpeg's fault, if it's so can
we workaround it or help fix libjpeg.
This stops pike76 from entering testing, thus being a part of lenny.
//Henrik Andreasson
On calling a stored procedure which has (results in) an empty resultset,
I get the following error message:
PROCEDURE {SPROC_NAME} can't return a result set in the given context
When looking up the error message on the MySQL website, the explanation
does not seem to match the problem, because when there is a result (one
or more) in the resultset, the problem does not occur.
What am I doing wrong?
(using the connect_option 0x20000 does not make a difference)
Greetings
Coen
…
[View More]__________________________________________________________
Deze e-mail en de inhoud is vertrouwelijk en uitsluitend bestemd voor de geadresseerde(n). Indien u niet de geadresseerde bent van deze e-mail verzoeken wij u dit direct door te geven aan de verzender door middel van een reply e-mail en de ontvangen e-mail uit uw systemen te verwijderen. Als u geen geadresseerde bent, is het niet toegestaan om kennis te nemen van de inhoud, deze te kopieren, te verspreiden, bekend te maken aan derden noch anderszins te gebruiken.
The information contained in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Please notify us immediately if you have received it in error by reply e-mail and then delete this message from your system.
__________________________________________________________
[View Less]
(["connect_options":2])
When I tried adding the above mapping to my code. Roxen started, but remains unreachable via a webbrowser. But, and this is the strange part, when I change the string literal from "connect_options" to for example "variable", Roxen starts and is available. Isn't this strange?! I know this is the exact cause for the change to occur, since it is truly the only thing that was changes.
Oh, I forgot to mention that I'm NOT EVEN USING the mapping :) . The error/strange …
[View More]behaviour purely results from creating the mapping:
catch {
mapping(string:int) tst_opt = (["connect_options":2]);
dbconn = Sql.Sql( QUERY(db_string));
};
I didn't get to the part of actually using the mapping yet.
__________________________________________________________
Deze e-mail en de inhoud is vertrouwelijk en uitsluitend bestemd voor de geadresseerde(n). Indien u niet de geadresseerde bent van deze e-mail verzoeken wij u dit direct door te geven aan de verzender door middel van een reply e-mail en de ontvangen e-mail uit uw systemen te verwijderen. Als u geen geadresseerde bent, is het niet toegestaan om kennis te nemen van de inhoud, deze te kopieren, te verspreiden, bekend te maken aan derden noch anderszins te gebruiken.
The information contained in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Please notify us immediately if you have received it in error by reply e-mail and then delete this message from your system.
__________________________________________________________
[View Less]