There is nothing special about the POCOs that you use with OrmLite, they are not tied to or linked to base tables, and there is no hidden magic state that OrmLite caches between calls so that it knows which fields it belongs to.
Each time DB is called, OrmLite simply uses POCO to create the corresponding SELECT, INSERT, UPDATE, or DELETE statements based on the definition of the schema type. INSERT Apis shows some examples of this.
Itβs best to think of OrmLite as turning your POCO into an SQL statement, which is. Therefore, an attempt to insert a ShipperTypeCount will attempt to insert an entry into a table named ShipperTypeCount if it does not have the [Alias("UseTableNameInstead")] attribute that will be used instead.
mythz source share