title

text

Peter Gribanov
Peter Gribanov
: December
22 мин

1С:Enterprise and PostgreSQL

  • 1С: as a cross-platform business application development environment
  • 1С and PostgreSQL together since 2006
  • 1C How to work with 1С on PostgreSQL in 1cFresh cloud service
  • What major improvements in 1С:platform make work with PostgreSQL more efficient.

Слайды

Видео

Другие доклады

  • Darafei Praliaskouski
    Darafei Praliaskouski Juno
    45 мин

    PostGIS for Disaster Management

    PostGIS is spatial extension for PostgreSQL.

    This talk will go in depth on using PostGIS for disaster management: which functions can be used and for what.

  • Teodor Sigaev
    Teodor Sigaev Postgres Professional
    Dmitry Belyavskiy
    Dmitry Belyavskiy ТЦИ
    22 мин

    LTREE: extending the syntax

    At the end of 2018, I've got a request to extend the syntax of the ltree contrib. I'm finalizing the patch and going to speak about:

    • the current state of the extension,
    • the extended syntax, and
    • the process of development and testing the extension.

  • Artemy Ryabinkov
    Artemy Ryabinkov Avito
    22 мин

    Best Practices and Practical Nuances when working with Postgres using Go

    In my talk I'll tell you about practices of working with Postgres in the Go-services. I’ll describe general advantages and disadvantages of the basic tools that are commonly used when working with Postgres using Go. Of course, we will touch on the nuances that need to be taken into account when your services are running inside the Kubernetes. I will also talk about Avito’s experience in providing a database of product’s developers. This presentation will be of interest to developers who want to avoid problems when working with Postgres, and will be useful to DBA who want to know what difficulties customers face in their database.

  • Alexey Fadeev
    Alexey Fadeev Sibedge
    45 мин

    ORM: how to write queries and not to drive database crazy

    Many DBMS specialists do not like these three letters - ORM because they have repeatedly seen the enormous queries ORM-generated for simplest operations. However practice shows that the origin of the problem is not ORM itself but rather those developers who are not able to use ORM properly. In this report I will tell you the basic principles of how to write code for ORM which generates "good" queries and also show you "bad" code samples and what you get out of them. The main idea is we have to think in SQL-style when writing the code, and so to learn to foresee what kind of query will be generated. But even having mastered that you must always check the output SQL for complex queries. I will show an example when a slight change in ORM-logic increases the volume of output SQL by dozens of times(!). I will tell you about additional tools and tricks. Namely - disabling tracking, INCLUDE construction, alternative syntax for JOIN, how to get more data using a smaller number of queries, how to effectively write queries with grouping, and what do we need mappings for. I will not bypass the cases when it is not possible to effectively solve the problem by means of ORM (for example, queries with recursion). In addition to SELECT requests, there are some Batch-Update/Delete tools that allow you to update and delete data using ORM tools without downloading data to the client side. We'll also talk on how to force the ORM to insert large volumes of data quickly via Multi-Insert and COPY. I will also discuss how ORM supports PostgreSQL-specific data types i.g. arrays, hstore and jsonb. But does it make sense to use ORM at all, since there is so much to learn? Sure it does. There are advantages of using ORM, and we will discuss them as well. All examples are based on Entity Framework technology for .Net Core and .Net Framework in C#. There are some subtle differences in ORM usage in Hibernate/NHibernate, but the basic principles remain the same, so the report will be useful for developers using various technologies.