This question is locked. New answers and comments are not allowed.
Does anyone know about Versant's FastObjects.NET product? I just ran across it on the net and watched their 30-minute video. My mouth hung open as I saw what appeared to be OpenAccess renamed! I mean exactly everything as if Vanatec sold / licensed to more than one company.
Check it out (it even uses the word "Extent" in the table names within queries just like OA):
Video:
http://www.versant.com/developer/resources/fastobjects/flash_presentation/introduction.html
Main Site:
http://www.versant.com/developer/resources/index
Let's hear some feedback.
Check it out (it even uses the word "Extent" in the table names within queries just like OA):
Video:
http://www.versant.com/developer/resources/fastobjects/flash_presentation/introduction.html
Main Site:
http://www.versant.com/developer/resources/index
Let's hear some feedback.
4 Answers, 1 is accepted
0
Hi Mark,
thanks for sharing your findings. OpenAccess got a long history and you found a partial outcome of it.
FastObjects is an object database (ODBMS) providing an API to deal with objects. Some engineers having defined and implemented that API moved over to create an API supporting ODBMS and RDBMS equally.
Adding Mapping and Runtime to the RDBMS-API made it an ORM, which was brought to market by Vanatec under the brand OpenAccess. Now it is all Telerik OpenAccess ORM being focused on .NET and RDBMS.
Extent relates to OQL, so that's why you would find it in all products supporting OQL.
Best regards,
Peter Brunner
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
thanks for sharing your findings. OpenAccess got a long history and you found a partial outcome of it.
FastObjects is an object database (ODBMS) providing an API to deal with objects. Some engineers having defined and implemented that API moved over to create an API supporting ODBMS and RDBMS equally.
Adding Mapping and Runtime to the RDBMS-API made it an ORM, which was brought to market by Vanatec under the brand OpenAccess. Now it is all Telerik OpenAccess ORM being focused on .NET and RDBMS.
Extent relates to OQL, so that's why you would find it in all products supporting OQL.
Best regards,
Peter Brunner
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
MWM
Top achievements
Rank 1
Rank 1
answered on 05 Feb 2009, 03:42 PM
Peter,
An interesting history indeed. Thanks of the info.
Hey, by the way, I contacted people affiliated with OQL and they responded that they see no mention of "extents" in the OQL definition (see my prior post: http://www.telerik.com/community/forums/orm/general-discussions/example-using-generics.aspx#726198) I've accepted the word in the language now, but I still think it's worth noting. Based on what I've read and I still might be incorrect, it seems it was something added by Vanatec.
An interesting history indeed. Thanks of the info.
Hey, by the way, I contacted people affiliated with OQL and they responded that they see no mention of "extents" in the OQL definition (see my prior post: http://www.telerik.com/community/forums/orm/general-discussions/example-using-generics.aspx#726198) I've accepted the word in the language now, but I still think it's worth noting. Based on what I've read and I still might be incorrect, it seems it was something added by Vanatec.
0
Hi Mark,
it's not an heritage of Vanatec or Versant, but from the FastObjects time...
The reason that deviation is -as far as I can remember- to make it more explicit which class extent was meant in cases where both a class Person and a class Persons are present in the database schema, when a simple pluralized name could mean different things.
Is that a bigger issue for you? If you don't want to have the keyword Extent in the query itself, you could also use the iterator definition form which also allows for a more precise type naming:
define extent mythings for Company.Mark.Things; select * from mythings as x where x.member ......
In this way, the type can have a full qualification with namespace (Company.Mark.Things), and the extent variable can be given a nice name without Extent.
Kind regards,
Thomas
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
it's not an heritage of Vanatec or Versant, but from the FastObjects time...
The reason that deviation is -as far as I can remember- to make it more explicit which class extent was meant in cases where both a class Person and a class Persons are present in the database schema, when a simple pluralized name could mean different things.
Is that a bigger issue for you? If you don't want to have the keyword Extent in the query itself, you could also use the iterator definition form which also allows for a more precise type naming:
define extent mythings for Company.Mark.Things; select * from mythings as x where x.member ......
In this way, the type can have a full qualification with namespace (Company.Mark.Things), and the extent variable can be given a nice name without Extent.
Kind regards,
Thomas
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
MWM
Top achievements
Rank 1
Rank 1
answered on 09 Feb 2009, 02:46 PM
Actually Thomas, I had noted "I've accepted the word in the language now", so I was just pointing out the odd similarity between the two products.
Thanks for your input however.
Thanks for your input however.