Possible race condition when inferring schema about rom-sql HOT 6 CLOSED

@paddor I can see that you have a method that creates the table in the relation class - this is probably the culprit because if you load relation classes without tables in the db, then inferring schemas can fail. Try moving this method to a different place. In general do not load relations and finalize rom setup if there are no tables yet. You can have db management tasks (create, drop, migrate etc.) with just rom configuration instantiated - there's no need for a finalized rom container.

from rom-sql.

@solnic I'm not sure if I understand correctly. I'm assuming by loading you mean the registration of the class in the config? The table creation is in a class method, called after creating the config and before creating a ROM container.

This is how the config and the container are instanciated:

          def initialize(uri)
            @config = ROM::Configuration.new :sql, uri do |config|
              config.register_relation Relation
              config.default.use_logger log
            end
          end


          def setup
            Relation.create_current_cases_table @config.gateways[:default]

            @container = ::ROM.container @config
            @repo = Repo.new @container
          end

#setup is called after initialization.

Should @config.register_relation Relation be done after creating the table?

from rom-sql.

The thing is that this error (failed to infer DB schema and thus methods like #by_path missing) also occured when the table already existed.

from rom-sql.

I'm assuming by loading you mean the registration of the class in the config?

Yes

The thing is that this error (failed to infer DB schema and thus methods like #by_path missing) also occured when the table already existed.

OK then disregard what I wrote. This is a tough one especially that there's no reproduction script. Auto-restriction methods are defined in the 'configuration.relations.schema.set' event which is triggered after a relation schema was established - this means there should be a table ready.

Notice that these methods are only defined for indexed columns - are you sure indices are defined in the db?

from rom-sql.

This was the DB schema:

sqlite3 current_cases.sqlite3 ".schema"
CREATE TABLE `current_cases` (`id` integer NOT NULL PRIMARY KEY AUTOINCREMENT, `path` varchar(255) NOT NULL UNIQUE, `object` blob NOT NULL);

Sometimes it worked, sometimes it didn't. The schema did not change.

I don't know if SQLite creates indices for PRIMARY KEY and UNIQUE columns.

from rom-sql.

@paddor yes it does. Would it be possible for you to create a reproduction script that mimics your prod setup?

from rom-sql.