Add support for a running number

[jerekarppinen]

Example config:

tables = {
   `customer` = {
     `name`   = 'MyCustomer' i
   }
}

outputs:

MyCustomer 1
MyCustomer 2
MyCustomer 3

[ppomes]

Hi @jerekarppinen,

Thanks for your request.

I just added this features. Can you pull the main branch, and check the tests tests/appendindex.conf and tests/prependindex.conf?

As you will see, you can new specify (append or prepend) a row index to a fixed value.

This should cover your needs, can you confirm?

Regards,
Pierre

[jerekarppinen]

Looks great!

Now I just have the first MyCustomer 1 twice:

DROP TABLE IF EXISTS `customer`;
/*!40101 SET @saved_cs_client     = @@character_set_client */;
/*!50503 SET character_set_client = utf8mb4 */;
CREATE TABLE `customer` (
  `id` int NOT NULL AUTO_INCREMENT,
  `name` varchar(255) NOT NULL,
  `other_table_id` int DEFAULT NULL,
  PRIMARY KEY (`id`),
  UNIQUE KEY `name` (`name`)
) ENGINE=InnoDB AUTO_INCREMENT=57 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci;

LOCK TABLES `customer` WRITE;
/*!40000 ALTER TABLE `customer` DISABLE KEYS */;
INSERT INTO `customer` VALUES (1,'MyCustomer 1',5846912),(2,'MyCustomer 1',5700228),(3,'MyCustomer 2',5770759) ....
/*!40000 ALTER TABLE `customer` ENABLE KEYS */;
UNLOCK TABLES;

I checked the original data and those two have different values.

Config used:

tables = {
   `customer` = {
     `name`   = appendindex 'MyCustomer '
   }
}

[ppomes]

Thanks for the test! This should be fix now, can you pull and try again?

Regards,
Pierre

[jerekarppinen]

It's fixed! Thanks!

[ppomes]

Thanks for your quick feedback. Issue closed!