[
https://issues.jboss.org/browse/TEIID-5285?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-5285:
-------------------------------------
[~shawkins] Updated the generated VDB based on current status. The original DB schema for
it is
{code}
DROP TABLE IF EXISTS ORDERS;
DROP TABLE IF EXISTS CUSTOMER;
CREATE TABLE CUSTOMER
(
ID bigint,
SSN char(25),
NAME varchar(64),
CONSTRAINT CUSTOMER_PK PRIMARY KEY(ID)
);
DROP TABLE IF EXISTS ORDERS;
CREATE TABLE ORDERS
(
ID bigint,
CUST_ID bigint,
orderdate date,
CONSTRAINT ORDER_PK PRIMARY KEY(ID),
CONSTRAINT CUSTOMER_FK FOREIGN KEY (CUST_ID) REFERENCES CUSTOMER (ID)
);
CREATE SEQUENCE IF NOT EXISTS customer_seq START WITH 200 INCREMENT BY 1;
CREATE SEQUENCE IF NOT EXISTS order_seq START WITH 200 INCREMENT BY 1;
{code}
Take look and let's figure out what modifications should/needs be done.
Add high-level feature for redirection of updates
-------------------------------------------------
Key: TEIID-5285
URL:
https://issues.jboss.org/browse/TEIID-5285
Project: Teiid
Issue Type: Feature Request
Components: Query Engine, Teiid Spring Boot
Reporter: Steven Hawkins
Assignee: Ramesh Reddy
Fix For: 11.x
Attachments: redirection-vdb.xml
In microservices testing it is desirable to test against production/live data but not
commit any updates. We should offer a simple solution that can defined by extension
metadata and enabled/disabled by a feature flag. We may need to make simplifying
assumptions about the scope (per session, per application, etc.) and durability of the
updates.
Under the covers this will be achieved by using views, update triggers, and a store for
the updates and when not enabled the expectation is that all operations should pass
through. However the application will be limited to using Teiid SQL and will be required
to use the Teiid or pg driver, or Teiid spring boot.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)