Telerik blogs

Tag: Telerik Data Access

  • Productivity

    Why OpenAccess does require transactions?

    OpenAccess relies on lazy loading and change tracking to make is as easy as possible for the user to work with persistent data. But we need a point in time where we can collect all changes in memory and execute the insert, update and delete statements to persist the changes. Typically this is the job of a transaction. The easiest way is to never let OpenAccess run without a started transaction. In this case you only have to call commit or...
    by Thomas Krueger
    May 27, 2021 2 min read
  • Productivity

    Reverse Mapping and Using Database Views with Telerik OpenAccess ORM

    We are glad to announce that one of the major improvements for our 2009 Q2 release is the support for database views. Views are stored queries accessed as virtual tables which represent the result of a query. To provide higher security, they can encapsulate the data into smaller result sets accessible from particular roles. Views are also used to combine data from many tables and allow the developer to expose the table data to the user in a more natural manner. Performance optimizations for fast searching and reading can be accomplished as well when using indexed views. Now with Telerik OpenAccess ORM...
    May 27, 2021 4 min read
  • Web

    Using Object Container to transport persistent objects between multiple pages

    We have talked already what are the best ways to handle the object scope instance in stateless environments like the Web in previous blog posts. We will build up on this and demonstrate additional web techniques, starting with using the same persistent objects on different pages (state sharing). Who needs that? Well let me explain a rather simplified scenario (but a valid one) – web-based wizard. Wizards usually have a workflow, which is produced by connecting web pages in a meaningful way. Every page is responsible for gathering data and providing navigation to the previous and next pages. This means...
    May 27, 2021 3 min read
  • Productivity

    Using the ObjectContainer in disconnected scenarios

    This is the first part of some postings regarding the ObjectContainer and I would like to start with a bit of motivation.   Why does the ObjectContainer exist? Because - we felt it is necessary to provide the same OpenAccess runtime environment in all tiers. Ideally, the business logic should not be concerned if it is running in a connected world (where the database can be directly contacted) or in a remote/disconnected tier (where no database can be accessed). The business logic should just find the same API to compile against so that it could be running in both scenarios. This is what the...
    May 27, 2021 2 min read
  • Productivity

    How to Enhance Projects Using MSBuild on a Machine Without Telerik OpenAccess ORM Installed

    Sometimes we need to  build Telerik OpenAccess ORM enhanced projects on a machine that has no installation of the OpenAccess product. There are cases that even require that there is no such installation done on the machines like build servers or other machines that handle the build process. On the other hand when Telerik OpenAccess ORM is installed, the project enhancement is automatically done from our Visual Studio integration add-in. The MSBuild integration can be used as an alternative to the Microsoft Visual Studio integration and is useful while using the command-line build environment. It is targeted for serving build...
    May 27, 2021 2 min read
Prev
... 31 32 33 34 35 36 37 38 39 40 ...
Next