Blog
All Blog Posts | Next Post | Previous PostTMS Aurelius Roadmap
Friday, January 27, 2012
TMS Aurelius has been released and we are very satisfied with feedback from all of you. Most comments are compliments and questions about how to use the existing many features, but some of them are also feature requests.So the intention of this post is to give you an idea of what's coming next with TMS Aurelius and TMS Data Modeler, based on customers feedback.
Please note that this list is subject to change, especially due to further customer feedback, and is not a commitment of any kind - we have the freedom to refrain from implementing any of these features - this is just the current intention for further development.
Features being considered to be implemented until 2.0 version:
- TObjectDataset component for visual binding objects to data-aware controls
- Support for more databases
- Support for more data-access components - IBObjects will be the next one to be supported
- Custom SQL expressions and projections
- More generator types - GUID should be the next one
- Other minor fixes and of course bug fixes
- More events and/or interceptors
Other features that are being considered (depending on feedback and demand):
- Dynamic properties
- Mapping through external file
- Database schema update (simple and limited)
- Query Language - use of query commands as alternative to query API
TMS Data Modeler will be improved as well, with support for more databases and constant improvements in user interface. And, of course, tighter integration with TMS Aurelius - improved class generation and constant support for new Aurelius features.
Wagner Landgraf
This blog post has received 36 comments.
Dynamic properties are a way to map properties to fields at runtime (not compile time) and depending on the database you are connecting to. In other words, it''s a way to use the same application to connect to two databases that are slightly different (some additional fields in some tables).
Wagner Landgraf
Thanks.
Karel Janecek
Wagner Landgraf
Ere Ebikekeme
Wagner Landgraf
Niek de Ruijter
Wagner Landgraf
Michael Trowe
Stephane Carre
2. Any plans to support SDAC, ODAC, IBDAC ?
Gerhard Holzner
2. UniDac support was added, can''t the same driver to be used with those components?
Wagner Landgraf
deksden
Wagner Landgraf
Example:
If you create the following entity:
[Entity]
[Table(''ARTISTS'')]
[Sequence(''SEQ_ARTISTS'')]
[Id(''FId'', TIdGenerator.IdentityOrSequence)]
TArtist = class
private
[Column(''ID'', [TColumnProp.Unique, TColumnProp.Required, TColumnProp.NoUpdate])]
FId: Integer;
...
it will NEVER work in SQLDirect or UniDac on an Oracle Database (fortunately it will work in DBExpress).
The reason is that SQLDirect and UniDac query components return an Oracle sequence value as a variant of double vartype, so the "Id" member of a TArtist object will not be assigned this value (an exception is raised).
As a solution, but an unpleasant one, we can declare Id property as Double in the TArtist entity class.
It would be nicer if Aurelius internally tried to cast the variant of double vartype to a variant of integer vartype.
Etienne Gwihen
Wagner Landgraf
Paolo Bocchini
wangwei
Wagner Landgraf
wangwei
Wagner Landgraf
ThePuyl
Wagner Landgraf
(next week ;-)?/next month?/next half year ?/next year ?)
ThePuyl
Wagner Landgraf
Thank you for the great product!
Michael Reisch
Cuomo Antonio
Wagner Landgraf
Valdenir Santana
Wagner Landgraf
p.field1 := p.field2 + p.field3
is not possible?
fields is float.
Cuomo Antonio
Gerhard Holzner
Wagner Landgraf
Wagner Landgraf
I''m afraid of the overhead of instantiating many business objects when there are many associations/joins between classes/tables.
For example, if I want to populate a grid with an overview of customer orders which shows the customer name and his address the order number and order date and order item details like produkt, price, etc. As far as I understand the concept means that populating the grid would mean that for each row I must create an instance for customer, order and order item to get the information I need but I just want to present an overview to the user with a simple ''dataset''. Finally when the user selects a concrete order I would instantiate the custumer, order and order item(s).
With HQL there is a SQL like query language supporting joins to present simple tabular data without the overhead of instantiating many business objects.
Maybe Aurelius Dataset has capabilities for this but if so I didn''t get it.
Gerhard Holzner
Wagner Landgraf
All Blog Posts | Next Post | Previous Post
Also, I didn''t understand what is dynamic properties
Magno Machado Paulo