> In addition, I'm still getting the erlydb_psql issues:
>
> ** exited: {undef,[{erlydb_psql,get_default_pool_id,[]},
> {erlydb,gen_module_code,5},
> {lists,foreach,2},
> {erlyweb_compile,compile,2},
> {erl_eval,do_apply,5},
> {shell,exprs,6},
> {shell,eval_loop,3}]} **
So I finally tracked this down. The following patch fixes it for psql
(but probably breaks it for mysql and mnesia):
Index: src/erlydb/erlydb.erl
===================================================================
--- src/erlydb/erlydb.erl (revision 210)
+++ src/erlydb/erlydb.erl (working copy)
@@ -378,7 +378,7 @@
TablesData =
case gb_trees:lookup(PoolId, PoolsData) of
- {value, Val} ->
+ {value, {ok,Val}} ->
Val;
_ ->
exit({invalid_erlydb_pool_option,
That is, PoolId was enclosed in an {ok, PoolId} tuple in
gen_module_code/5. I'll have to poke around to see where it's
happening, but if anyone knows off of the top of their head, let me
know, since I probably won't get a round tuit until at least this
weekend.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"erlyweb" 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/erlyweb?hl=en
-~----------~----~----~----~------~----~------~--~---
