Kai Voigt wrote:
>a stored procedure in MySQL doesn't return anything itself, but it
>might include one or more SQL statements which are returned to the
>calling client as if those statements would have been called
>individually.
>Note that you might have to handle multiple statements in a stored
>procedure.
I see.
So I presume that stored procedures in MySQL are not invoked through
mere SELECTs?
It would imply, though, that if you stick to at most one SELECT …
[View More]resultset
in your MySQL stored procedure, then the current Sql interface in Pike
will/should suffice.
Oracle and PostgreSQL can return at most a single resultset, and are invoked
through SELECT normally.
--
Sincerely,
Stephen R. van den Berg.
"<Clarions sounding> *No one* expects the Spanish inquisition!"
[View Less]
Is there a particular reason this doesn't work:
Pike v7.8 release 127 running Hilfe v3.5 (Incremental Pike Frontend)
> Stdio.FILE in;
> (in=Stdio.FILE())->assign(Stdio.FakeFile("foo\nbar\n"));
Stdio.File(): not open.
/usr/local/pike/7.8.127/lib/modules/Stdio.pmod/module.pmod:1490:
Stdio.FILE(0, 0, 777 /* fd=-1 */)->set_read_callback(0)
/usr/local/pike/7.8.127/lib/modules/Stdio.pmod/module.pmod:1192:
Stdio.FILE(0, 0, 777 /* fd=-1 */)->set_read_callback(…
[View More]0)
/usr/local/pike/7.8.127/lib/modules/Stdio.pmod/module.pmod:727:
Stdio.FILE(0, 0, 777 /* fd=-1 */)->assign(Stdio.FakeFile(8,"rw"))
/usr/local/pike/7.8.127/lib/modules/Stdio.pmod/module.pmod:1776:
Stdio.FILE(0, 0, 777 /* fd=-1 */)->assign((a)0=Stdio.FakeFile(8,"rw"))
>
--
Sincerely,
Stephen R. van den Berg.
I'm sorry. The number you have reached is imaginary.
Please rotate your phone 90 degrees and try again.
[View Less]
Arne Goedeke wrote:
>Stephen R. van den Berg wrote:
>>> Stdio.FILE in;
>>> (in=Stdio.FILE())->assign(Stdio.FakeFile("foo\nbar\n"));
>> Stdio.File(): not open.
>Not sure what you expect it to do. Stdio.File operates on an fd,
>FakeFile does not have any. I think that assign is meant to be used for
>Stdio.File subclasses primarily.
Well, I'd like to have a FakeFile() with getchar(), gets() and unread().
So I thought, opening a Stdio.FILE() with a FakeFile()…
[View More] as source should
do the trick.
--
Sincerely,
Stephen R. van den Berg.
The first 90% of code accounts for the first 90% of development time.
The remaining 10% of code accounts for the other 90% of development time.
[View Less]
Pike 7.8 currently does:
> ({"abc",({65,65,66}),"def"})*"x";
(1) Result: "abcxdef"
I have created a patch that makes it do:
> ({"abc",({65,65,66}),"def"})*"x";
(1) Result: "abcxAABxdef"
instead, and which also throws an error if any other types are inside
the array (the old code merely skipped them).
I'd consider the second behaviour (after my patch) more desirable and
in light of actually throwing errors on unsupported types, it is really
is a bugfix.
Any objections to this behaviour?…
[View More]
--
Sincerely,
Stephen R. van den Berg.
Auto repair rates: basic labor $40/hour; if you wait, $60; if you watch, $80;
if you ask questions, $100; if you help, $120; if you laugh, $140.
[View Less]
Hi,
I need an example for using the AES encryption in pike 7.4. I can't get
it to work. Thanks a bunch!
--
Met vriendelijke groet / With kind regards / mit besten Grüßen,
Coen Schalkwijk
Software Engineer
coen.schalkwijk(a)rtl.nl <mailto:coen.schalkwijk@rtl.nl>
coen(a)rtlinteractief.nl <mailto:coen@rtlinteractief.nl>
+31 (0)35 671 8915
__________________________________________________________
Deze e-mail en de inhoud is vertrouwelijk en uitsluitend bestemd voor …
[View More]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]
This looks fine:
> string a=({"12","34","56"});
Compiler Error: 1: Bad type in assignment.
Compiler Error: 1: Expected: string.
Compiler Error: 1: Got : array(string(0..255)).
This is confusing:
> (string)({"12","34","56"});
cast: Item 2 is not an integer: "56"
HilfeInput:1: HilfeInput()->___HilfeWrapper()
Any ideas on how this last one can be improved?
--
Sincerely,
Stephen R. van den Berg.
E-mails should be like a lady's skirt:
Long enough to cover the subject, …
[View More]and short enough to be interesting.
[View Less]
6
6
Stdio.exist
by Martin Stjernholm, Roxen IS @ Pike developers forum
01 Feb '09
01 Feb '09
I just noticed that Stdio.exist returns 0 for dangling symlinks. I
think that's unfortunate.
What do you say, consider it a bug and fix it (with compat goo for
#pike 7.6), or document it as intended behavior?
There is a SHA (or sha) function provided by Pike 7.4 in the Crypto
class. But is this SHA-0 or SHA-1?
--
Met vriendelijke groet / With kind regards / mit besten Grüßen,
Coen Schalkwijk
Software Engineer
coen.schalkwijk(a)rtl.nl <mailto:coen.schalkwijk@rtl.nl>
coen(a)rtlinteractief.nl <mailto:coen@rtlinteractief.nl>
+31 (0)35 671 8915
__________________________________________________________
Deze e-mail en de inhoud is vertrouwelijk en uitsluitend bestemd voor de …
[View More]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]