I am still trying to get mysql working. Here is a update of my research.
1) I used meld to get a overview of the changes in libape_spidermonkey.c
between:
fa5311f90ed21f3ff538b9578a9d5d31fb5a1fb3 2012-06-23 14:01:12 (the last
commit with mysql working)
and
abe51a039712e67643c655b6abfa7a0e751f8014 2012-06-25 12:49:39 (the first
one after the 1.8.2 update that immed compiles with out problems)
2) As mentioned in my earlier post, the mysac_setup makes a good connection
(I can see that in mysql.log)
3) From there I sprayed lots of printf's in both versions and it appears to
go wrong in mysac_setdb_success;
JS_CallFunctionName(myhandle->cx, myhandle->jsmysql, "onConnect", 0, NULL,
&rval);
fa3211 returns JS_TRUE, rval looks ok
abe51 returns JS_TRUE, rval is rubish
4) if I replace "onConnect" with "getInsertId", then in both cases
apemysql_sm_insert_id is called, so it seems that myhandle has a valid
context and a valid object instance.
it seems that onConnect is not defined for that object, but the
"JS_FS("onConnect", ape_sm_stub, 0, 0)," in apemysql_funcs looks ok.
Does any body have some clues to share?
Peter
>
>
>
--
You received this message because you are subscribed to the Google
Groups "APE Project" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/ape-project?hl=en
---
APE Project (Ajax Push Engine)
Official website : http://www.ape-project.org/
Git Hub : http://github.com/APE-Project/
