Skip to main content
GuideServerConfigure and deploy Tabsdata servers on your machine.TutorialsConfigure data integration workflows within a running Tabsdata server.Advanced TutorialsBuild end-to-end workflows between two specific systems.API ReferenceCLI ReferenceRelease Notes
Version: 2.0.2

Update a Collection

AI agent session
rename the subscriptions collection to billing and describe it as invoicing and dunning transformers

Called tabsdata 2 times (ctrl+o to expand)

Renamed. The functions and tables inside kept their names; only the collection changed.

┌───────────────┬────────────────────────────────────┐
│     field     │               value                │
├───────────────┼────────────────────────────────────┤
│ name          │ billing                            │
├───────────────┼────────────────────────────────────┤
│ previous name │ subscriptions                      │
├───────────────┼────────────────────────────────────┤
│ description   │ Invoicing and dunning transformers │
├───────────────┼────────────────────────────────────┤
│ group         │ default                            │
├───────────────┼────────────────────────────────────┤
│ type          │ data product                       │
├───────────────┼────────────────────────────────────┤
│ connection    │ none                               │
└───────────────┴────────────────────────────────────┘

Two things this does not do. It cannot move the collection to another group, so the type stays what it was. And on a source or destination collection a rename renames the connection too, since the connection is named by its collection.