Collection MappingNaming conventions All the tables and columns in the database are all lowercase. (Which is quite handy with an Mysql database because the names are case-sensitive if the underlying file system is also case-sensitive. So Mysql Names are case sensitive on Linux but not on Windows.) Tablenames are plural. Prototype names start with upper case and are camel case. Prototype names are singular. Property- Object- and Collection-Mapping start with lower case and are also camel case. Foreign keys are prefixed with the name of the table they are referring to. 1:n relationDB schema
Mapping Gallery/type.propertiesm:n relationDB schema
Mapping Image/type.properties
The Backslash "\" is only necessary when you have a filter that continues in the next line. Pages linking to this page: Documentation Drafts |
navigation
Download
Community
Weblog
Mailing Lists
IRC Channel
Documentation
Introductions
Tools
Reference
Project
Roadmap
Bug Reporting
Source
Wiki
Tags
Updates
Related Projects
Sites using Helma
Shop
search
tags for this page
all tags
Tagsapps (1) bugs (2) class (1) community (2) compatibility (1) concurrency (1) continuations (2) Documentation (4) Documentation ORM (1) dogfood (1) formatting (1) gobi (1) helma (6) helma 1.6 (13) helma 1.7 (8) helma 2 (13) helma ng (7) hopobject (1) html (1) inheritance (5) introspection (1) java (2) javascript (5) jetty (1) JSDoc (1) lazy (1) marius person (1) metaprogramming (2) modules (3) oop (1) organization (2) ORM (1) parsing (1) project (2) projects (1) prototype (1) Rabbit (2) REPL (1) rhino (4) roadmap (3) shell (1) shop (0) Skin Rendering (5) Snippets (1) source svn (1) sugar (3) templates (13) testing (4) Tobi (7) tobi repl shell introspection (0) xml (1) Pages linking to this page: Wiki Overview Text Draft pages linking here
|
Comments
#1 by maks at 2008/05/09 05:09While the above works well as a "view" for m:n mappings, it cannot currently be used as a normal collection, as Helma is Not able to add new objects to collections that have filters defined.