SQL refers to itself. What's the OBD pattern?



  • There are: (1) UL (Legal person, company) with properties: Name, INN, PRG; (2) FL (physical person, character) with properties: FIO, INN

    Between these things, there's a connection between the creatures, "Integrated," which characterizes the nature of the debt. UL may have several founders who may be both FL and UL. Please provide advice on which OBD scheme is suitable for the storage of copies of these properties and links;



  • I would do that.

    First table with yuriks (UL)

    Second table with physics (FL)

    And two communication tables (LINKS_UL, LINKS_FL)

    create table LINKS_UL(
        id int foreign key UL(id),
        related int foreign key UL(id)
    )
    

    create table LINKS_FL(
    id int foreign key UL(id),
    related int foreign key FL(id)
    )

    But there's a lot on how to use the data.




Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2