[JBoss JIRA] (TEIID-5773) Allow for generated_key retrieval at a session level
by Steven Hawkins (Jira)
Steven Hawkins created TEIID-5773:
-------------------------------------
Summary: Allow for generated_key retrieval at a session level
Key: TEIID-5773
URL: https://issues.jboss.org/browse/TEIID-5773
Project: Teiid
Issue Type: Sub-task
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 12.3
The docs suggest that generated_key should be called in a procedure. However calling outside of a procedure will currently return no values as the keys are associated with the executing command context only. Ideally from a connection the user should be able to do:
insert into ...;
select generated_key() ...;
In separate statements and still retrieve the key value.
The workaround is to use an anonymous procedure block:
begin
insert into ...;
select generated_key() ...;
end
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (TEIID-5763) GENERATED_KEY returns NULL if used in INSTEAD OF INSERT Triggers in DDL files
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5763?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5763:
----------------------------------
Fix Version/s: 12.3
Priority: Critical (was: Blocker)
Marking complete for issues highlighted as 1/3 - where 1 required a code change to always fetch generated keys, and 3 was largely a doc issue. Also added a more convenient generated_keys function and updated the docs with that.
> GENERATED_KEY returns NULL if used in INSTEAD OF INSERT Triggers in DDL files
> -----------------------------------------------------------------------------
>
> Key: TEIID-5763
> URL: https://issues.jboss.org/browse/TEIID-5763
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 12.2
> Reporter: Christoph John
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 12.3
>
>
> The issue arrised in:
> https://developer.jboss.org/message/989700#989700
> Following sceanarios are given:
> Variant 1:
> Table Product(id), primary key = autoincrement;
> Table QuicklyAddedProduct, primary key is foreign key on Product.id
> Table Diary_SRC
> View Diary on Diary_SRC
> INSTEAD OF INSERT Trigger on Diary should :
> -create new record on Product,
> -get autoincremented Product.id of new record,
> - create new QuicklyAddedProduct with returned Product.id as primary key
> - create new Diary record with QuicklyAddedProduct
> {
> INSERT a new record on Product;
> idProduct = CONVERT(GENERATED_KEY('idProduct'),long); // fails
> }
> Variant 2:
> INSTEAD OF INSERT trigger on Diary should :
> - create new QuicklyAddedProduct
> - add Quickly added prodcut to Diary
> additionally a INSTEAD OF trigger on QuicklyAddedProduct exists which:
> - creates new Product record
> - uses returned GENERATED_KEY(Product.id) to add record on QuicklyAddedProduct with Product.id as primary key
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (TEIID-4251) Built in support for Postgres DB as materialization target
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-4251?page=com.atlassian.jira.plugin... ]
Work on TEIID-4251 started by Steven Hawkins.
---------------------------------------------
> Built in support for Postgres DB as materialization target
> ----------------------------------------------------------
>
> Key: TEIID-4251
> URL: https://issues.jboss.org/browse/TEIID-4251
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.3
>
>
> If Postgres database is available along with install or assumed that it is available, then some of the materialization task can be automated, like
> - Creation of a common STATUS table
> - Creation of the materilization targets (create views on dbms)
> - On load, on undeploy and load scripts for all the materialization views
> We need to device a way this to be pluggable, such that based on success of this, we can provide additional support for other sources.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (TEIID-5772) Issues with binary/streaming values in odata
by Steven Hawkins (Jira)
Steven Hawkins created TEIID-5772:
-------------------------------------
Summary: Issues with binary/streaming values in odata
Key: TEIID-5772
URL: https://issues.jboss.org/browse/TEIID-5772
Project: Teiid
Issue Type: Bug
Components: OData
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 12.3
There are two issues:
1. The hasStream method always returned false.
2. There wasn't proper handling for BinaryType in outputting values. The java serialized value, not the simple byte value was presented.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months
[JBoss JIRA] (TEIID-5704) Support openapi 3 sources
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5704?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-5704.
-----------------------------------
Resolution: Done
Updated the docs, added wildfly support and an arquillian test (using odata openapi v2/v3 metadata).
> Support openapi 3 sources
> -------------------------
>
> Key: TEIID-5704
> URL: https://issues.jboss.org/browse/TEIID-5704
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.3
>
>
> It seems like a good idea to introduce a new translator, rather than trying to fit openapi 3 support onto the swagger translator - as the io.swagger libraries and a lot of logic will be different.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 6 months