Question 1

How do I add sequential IDs to an existing table with Sequenced?

Accepted Answer

You need to write a migration that adds the column and updates existing records using SQL, like the README example where ROW_NUMBER() sets IDs based on scope, ensuring data integrity before adding constraints.

Question 2

Sequenced gem vs using Rails' built-in counter cache?

Accepted Answer

Sequenced is for scoped sequential IDs within parent contexts, while counter cache counts associations; Sequenced offers more control over numbering and custom scopes but requires more setup like indexes.

Question 3

Can I skip generating a sequential ID for certain records?

Accepted Answer

Yes, use the `skip` option with a lambda to conditionally skip ID generation, such as when a record's score is zero, allowing flexible business logic integration.

Question 4

What database indexes should I add for Sequenced?

Accepted Answer

Add a unique index on the sequential ID column and scope columns to prevent duplicates and improve performance, as recommended in the schema integrity section with examples.

Question 5

How does Sequenced handle polymorphic associations?

Accepted Answer

Scope by multiple columns, e.g., [:questionable_id, :questionable_type], to support polymorphic relationships, ensuring sequential IDs are unique per polymorphic parent object.

Question 6

Is Sequenced safe for high-traffic apps with concurrent writes?

Accepted Answer

Only if using PostgreSQL; for other databases, you may need additional locking or error handling to avoid race conditions, as the gem lacks built-in concurrency support.

Sequenced

What is Sequenced?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions