RFC: Optional property type declarations for embedded dbProposal:Currently when using a SQL DB, its possible to fetch DB metadata (via JDBC) from the HopObject property->DB table-column mapping in type.properties files, and use the metadata to determine the type of each property. No such facility currently exists for the embedded xml-based DB. ImplementationApprove and document the use of optional type specifications in type.properties files when Prototypes are using the embedded db data-store.Eg. Book/type.properties
After some initial testing, this seems to actually work ok (as of helma 1.6.1) and the type values are available to JS app code now via:
Though I nicer API could be defined in by adding for example:
method to helma.framework.core.Prototype for example. The availability of this API for introspection of Protype definitions would make it much easier for applications to do simple data validation and also to create other useful utils. |
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
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 |