Cache's multiple interfaces (RDMBS, OO) can cause confusion even for simple operations, such as inserting dates. Here is how that is done:
In SQL:
insert into CM.StrmClass(PatientAddress, PatientName, PatientDateOfBirth)
values('5 Soi Rangnam Bangkok, Thailand', 'TG', {d '1990-03-17'})
Rather ugly ODBC formatting for the date field. In Object Script:
Set p.PatientDateOfBirth = $ZDateh("12/21/1977")
By the way, if a %Save fails (does not make the results commit to the database), then there is a problem with the data validation. Running the container from the Terminal should show the result (e.g. W p.%Save())
Another interesting feature of Cache, which accounts for its performance: 'Using a unique feature known as “subscript mapping,” you can specify how the data within one or more arrays is mapped to a physical database file. Such mapping is a database administration task and requires no change to class/table definitions or application logic. Moreover, mapping can be done within a specific sparse array; you can map one range of values to one physical location while mapping another to another file, disk drive, or even to another database server. This makes it possible to reconfigure Caché applications (such as for scaling) with little effort.'
