Hopbot log for 2008-02-25 - Helma IRC channel: #helma on irc.freenode.net

2008-02-25:

[1:50] <bmp> I have two key questions on HopObjects and their mappings to RDBMSes:
[1:50] <bmp> First, I can't figure out how to handle a complex key. Is the answer simply that they aren't supported?
[1:51] <bmp> Second, I can't figure out how to represent relationships that are not hierarchical. In an OODBMS, I could handle that by having the same object appear in two different structures. In an RDBMS, we're just talking about foreign keys in multiple places. In Helma, I can't quite figure out a way to represent what I want.
[7:02] <zumbrunn> hi bmp
[7:03] <zumbrunn> I believe for the purpose of the object/relational mapping in helma you need a simple key
[7:03] <zumbrunn> oops, you just left
[7:04] <zumbrunn> anyway, you might want to take both those questions to the helma-user mailing list
[7:05] <zumbrunn> you can define multiple parent mappings and access the same object through different collections
[7:05] <zumbrunn> http://helma.org/docs/guide/mapping/basic/
[8:48] <jkridner> I have a quick question. What is the easiest way to serve favicon.ico?
[8:49] <jkridner> I think making an action is difficult, because of the '.'.
[8:51] <jkridner> nm, I guess it works to just put it in the markup.
[9:30] <zumbrunn> jkridner: actually actions with a period in their name work just fine
[9:30] <zumbrunn> additionally, you can use a underscore in place of the period
[9:30] <zumbrunn> helma will automatically substitute that appropriately
[9:31] <zumbrunn> also, you could use a link tag to point to the fav icon
[9:31] <zumbrunn> <link rel="shortcut icon" href="http://dev.helma.org/static/files/0/helma.ico" type="image/vnd.microsoft.icon" />
[9:32] <zumbrunn> or catch and redirect the requests to /favicon.ico with apache before they get to jetty/helma
[9:33] <zumbrunn> or catch them using an onRequest handler
[9:34] <zumbrunn> or using the notfound handler
[9:34] <zumbrunn> many ways lead to rome

 

 

In the channel now:

Logs by date: