Thanks for the question and the reply. I think I need to state clearly in the documentation that the psql driver is alpha quality. A few people have run into problems with it but unfortunately I haven't gotten any patches to fix it. I don't maintain it myself because I use MySQL.
In general, though, I think ErlyWeb is great for fast development once you get it running, and it's reasonably simple to get it running at least with Unix/MySQL, which is what most people use. It's ironic, though, because once of the reasons I was moved to Erlang was that I spent like half a day trying to install Rails and got so frustrated I just wanted to use something simpler. Yariv On Sat, Sep 27, 2008 at 3:49 PM, Ulf Wiger <[EMAIL PROTECTED]> wrote: > > Quod licet Jovi non licet Bovi... ;-) > > Personally, I wasted a week of my life trying to do /anything/ > at all with Rational Rose Realtime, and have failed several > times installing Eclipse (once due to some lock violation error > on a dual-core Vista machine). I've spent several days testing > various web development and groupware frameworks and > being stumped by missing perl libs, inconsistent installs, > version mismatches, etc. > > I'm not trying to belittle your pain. It should be easier, but > in my experience, "production quality" tools in the mainstream > can often (not always, of course) be just as difficult, or much more > difficult, to get going with. > > The problem is of course when there are well-known alternatives > that give less pain. That certainly lowers the tolerance threshold > for this kind of noise, but I would like to suggest that you prepare > yourself for some friction if you decide to try out a tool supported by > a very small community, and you choose an OS and a database > backend other than the preferred options (unix/mysql). > > The ErlyWeb docs do state pretty clearly that only MySQL is > supported, so it shouldn't be too surprising that they don't > describe in detail how to get going with Postgres. > (http://erlyweb.org/doc/erlydb.html) > > Also, ten seconds with google revealed the following info > about installing yaws on windows: > > http://bloggablea.wordpress.com/2007/04/21/building-yaws-for-windows/ > http://yaws.hyber.org/wiki/showOldPage.yaws?node=YawsAndWin32&index=1 > http://groups.google.com/group/erlyweb/web/erlyweb-erlang-windows-installation?pli=1 > > BR, > Ulf W > > 2008/9/27 Steve <[EMAIL PROTECTED]>: >> >> Given a task to implement a quick web service, I thought I'd try >> erlang/yaws/erlyweb to build it. Reading the fluff, it seems this >> should be "easy" and "fast" to do. >> >> 1) Yaws didn't install right on the development platform available >> (windows). I read the yaws documentation completely but in the end I >> had to piece it together from digging around in the yaws code to >> understand the structure of yaws to get a decent install. >> (time wasted: approx 3 hours) >> >> 2) Again, there wasn't *any* correct documentation to explain how to >> connect to the required database (postgres) but fortunately I found >> this blog post... >> http://cdrinpeace.wordpress.com/2008/06/09/configuring-erlyweb-with-postgres/ >> (time wasted: approx 2 hours) >> >> 3) With everything supposedly running correctly, I finally got the >> error message below (returned from postgres). Again scanning at code >> level I found that this is a problem not with the driver (psql) nor >> erlyweb but in the erlydb code itself (i.e. erlsql -- the error >> message below should be more than sufficient to find/fix the problem >> if you have the time/interest). Short of rewriting the platform code >> (!!not acceptable - we cannot be expected to maintain a branch of the >> erlang code!!), or waiting for an official fix release (there is >> little doubt this would be outside our schedule) this ended up as a >> project blocker. >> (time wasted: approx 2-3 hours) >> >> Result: Having wasted essentially a DAY on this, I gave up and used >> Tomcat instead. >> >> LESSON LEARNED: Given that achieving even the simplest project runs >> into all sorts of delays, It should be OBVIOUS why erlang/erlyweb is >> not hot news for web developers/web development!!! >> >> The final straw was.... >> >> ERROR erlang code crashed: >> File: appmod:0 >> Reason: {function_clause, >> [{lists,foldl, >> [#Fun<erlydb_psql.2.79238577>,[], >> {sql_error,"42601", >> "Rbase_yyparse L5868 Fgram.y HUse separate LIMIT >> and OFFSET clauses. MLIMIT #,# syntax is not supported"}]}, >> {erlydb_psql,get_select_result,2}, >> {erlydb_base,select,3}, >> {erlyweb_controller,list,3}, >> {erlyweb,ewc,2}, >> {erlyweb,handle_request,6}, >> {yaws_server,deliver_dyn_part,8}, >> {yaws_server,aloop,3}]} >> Req: {http_request,'GET', >> {abs_path,"/namelookup//agent/list/1"}, >> {1,1}} >> >> >> > >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
