Just some of the stuff I found while reading up on Mumps:
>>M has many good points: high productivity, low hardware requirements, good
scalability. But M also has some weaknesses: low transaction
character-based screens, poor integration with other environments, and
[Thomas C. Salander, M Computing, June 1994, p.74]
M is a lousy language with one great data type.
[Steve J. Morris]<<
Do these still apply?
>>7. Why is M called a "database language?"
M is a programming language with a strong emphasis on text
handling and database management. However, M is NOT a data base
management system. The disadvantage of being a programming language is
it takes more expertise to apply the language to create a working data
but the advantage of not being a dedicated database management system
is that it is infinitely more flexible.<<
This would seem to make it very hard to use for my purpose (which needs
Perusing the manual I could find no mention of object-level access
What kind of security model does Mumps or GT.M use? And is there a good
reference around? The book mentioned earlier won't be in for weeks (they
have it in stock -- imagine that). I'm looking for texts on
constructs, introspection, and pointers/references in the database.