{* ../../docs_src/sql_databases/tutorial001_an_py310.py ln[1:11] hl[7:11] *}

The `Hero` class is very similar to a Pydantic model (in fact, underneath, it actually *is a Pydantic model*).

There are a few differences:

* `table=True` tells SQLModel that this is a *table model*, it should represent a **table** in the SQL database, it's not just a *data model* (as would be any other regular Pydantic class).

    }

    @Test
    @DisplayName("Test sign method with different offsets")
    void testSignWithDifferentOffsets() {
        // Arrange
        byte[] largeData = new byte[100];
        for (int i = 0; i < largeData.length; i++) {
            largeData[i] = (byte) i;
        }

        // Test with different offsets
        int[] offsets = { 0, 10, 50, 90 };

        for (int offset : offsets) {

        assertEquals("000000FF", Hexdump.toHexString(255, 8));
        assertEquals("00001000", Hexdump.toHexString(4096, 8));
        assertEquals("FFFFFFFF", Hexdump.toHexString(-1, 8));

        // Test different sizes
        assertEquals("00", Hexdump.toHexString(0, 2));
        assertEquals("FF", Hexdump.toHexString(255, 2));
        assertEquals("1234", Hexdump.toHexString(0x1234, 4));
    }

    @Test

        // Different instances
        assertFalse(CrawlerStatus.INITIALIZING.equals(CrawlerStatus.RUNNING));
        assertFalse(CrawlerStatus.INITIALIZING.equals(CrawlerStatus.DONE));
        assertFalse(CrawlerStatus.RUNNING.equals(CrawlerStatus.DONE));

        // Null comparison
        assertFalse(CrawlerStatus.INITIALIZING.equals(null));

        // Different type comparison

 * class was added for Java 8. The two classes are extremely similar, but incompatible (they cannot
 * share a common supertype). <i>All</i> known differences are listed either here or with the
 * relevant methods below.
 *
 * <ul>
 *   <li>This class is serializable; {@code java.util.Optional} is not.

Here **FastAPI** won't get confused because you are using `Depends`.

///

/// check

The way this dependency system is designed allows us to have different dependencies (different "dependables") that all return a `User` model.

We are not restricted to having only one dependency that can return that type of data.

///

## Other models { #other-models }

  private val provider: Provider =
    org.openjsse.net.ssl
      .OpenJSSE()

  // Selects TLSv1.3 so we are specific about our intended version ranges (not just 1.3)
  // and because it's a common pattern for VMs to have differences between supported and
  // defaulted versions for TLS based on what is requested.
  override fun newSSLContext(): SSLContext = SSLContext.getInstance("TLSv1.3", provider)

        // I'm fully aware that the file could just be moved using File.rename but
        // there are bugs in various JVM that have problems doing this across
        // different filesystem. So we'll incur the small hit to actually copy
        // here and be safe. jvz.
        // ----------------------------------------------------------------------------

        try {

/// tip | Consejo

If CSI Migration is working properly, Kubernetes end users shouldn’t notice a difference.
After migration, Kubernetes users may continue to rely on all the functionality of in-tree storage plugins using the existing interface.