July 2014 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2234) Unable to set numeric bounds to values greater than 999999

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2234?page=com.atlassian.jira.plu... ] Barry LaFond edited comment on TEIIDDES-2234 at 7/21/14 11:04 AM: ------------------------------------------------------------------ org.teiid.designer.xsd.ui.editor.FacetHelper hard-codes the max limit: public static final int DEFAULT_MAX_BOUNDS = 999999; public static final int DEFAULT_MIN_BOUNDS = -DEFAULT_MAX_BOUNDS; Not sure what our limit should be... suggestions? Java stores all integers in memory as binary numbers. name bytes bits minimum maximum byte 1 8 -128 +127 short 2 16 -32,768 +32,767 int 4 32 -2,147,483,648 +2,147,483,647 long 8 64 -9,223,372,036,854,775,808 +9,223,372,036,854,775,807 was (Author: blafond): org.teiid.designer.xsd.ui.editor.FacetHelper hard-codes the max limit: public static final int DEFAULT_MAX_BOUNDS = 999999; public static final int DEFAULT_MIN_BOUNDS = -DEFAULT_MAX_BOUNDS; Not sure what our limit should be... suggestions? > Unable to set numeric bounds to values greater than 999999 > ---------------------------------------------------------- > > Key: TEIIDDES-2234 > URL: https://issues.jboss.org/browse/TEIIDDES-2234 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Modeling > Affects Versions: 8.3.3 > Environment: JBoss Developer Studio 7 on Mac OS X Mavericks > Reporter: Sean Haynes > > Creating a XSD Simple Type Model in the TEIID editor. Numeric values (tried integer, decimal, and float types) do not allow bounds to be set greater 999,999. If the XSD is edited manually, the designer will revert the value back to 999,999 if you click on the type that has manually edited value. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2256) Confusing data type "integer" and "int"

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2256?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-2256: ------------------------------------------ xs:integer is derived from xs:decimal. Are you seeing some of the type hierarchy rather than the runtime mapping? > Confusing data type "integer" and "int" > --------------------------------------- > > Key: TEIIDDES-2256 > URL: https://issues.jboss.org/browse/TEIIDDES-2256 > Project: Teiid Designer > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Ramesh Reddy > > I understand that > "integer" maps to "xs:biginteger" > "int" maps "xs:long" > How they are confusing when there is already one available for biginteger. Also the Table creation wizard does not provide option to to select "int". When user chooses "integer" it often is "int". > This confusion needs to be resolved. IMO "integer" can be removed, however I am not sure how it effects data type system -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2256) Confusing data type "integer" and "int"

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2256?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2256: ---------------------------------------- sorry it is designed as integer -- xs:decimal > Confusing data type "integer" and "int" > --------------------------------------- > > Key: TEIIDDES-2256 > URL: https://issues.jboss.org/browse/TEIIDDES-2256 > Project: Teiid Designer > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Ramesh Reddy > > I understand that > "integer" maps to "xs:biginteger" > "int" maps "xs:long" > How they are confusing when there is already one available for biginteger. Also the Table creation wizard does not provide option to to select "int". When user chooses "integer" it often is "int". > This confusion needs to be resolved. IMO "integer" can be removed, however I am not sure how it effects data type system -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2256) Confusing data type "integer" and "int"

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2256?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-2256: ------------------------------------------ Maybe a clarification is needed. Where is xs:biginteger coming from? > Confusing data type "integer" and "int" > --------------------------------------- > > Key: TEIIDDES-2256 > URL: https://issues.jboss.org/browse/TEIIDDES-2256 > Project: Teiid Designer > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Ramesh Reddy > > I understand that > "integer" maps to "xs:biginteger" > "int" maps "xs:long" > How they are confusing when there is already one available for biginteger. Also the Table creation wizard does not provide option to to select "int". When user chooses "integer" it often is "int". > This confusion needs to be resolved. IMO "integer" can be removed, however I am not sure how it effects data type system -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2256) Confusing data type "integer" and "int"

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2256?page=com.atlassian.jira.plu... ] Barry LaFond edited comment on TEIIDDES-2256 at 7/21/14 10:22 AM: ------------------------------------------------------------------ Our design-time types are defined here: https://github.com/Teiid-Designer/teiid-designer/blob/master/plugins/org.... Except for adding *varbinary* 2 years ago, nothing's been changed for quite some time. 1) Would it be safe to just remove the xs:biginteger? 2) Maybe just adding a validation warning (deprecate?) would be enough? 3) Could you check this schema for any other types that should be there? was (Author: blafond): Our design-time types are defined here: https://github.com/Teiid-Designer/teiid-designer/blob/master/plugins/org.... Except for adding *varbinary* 2 years ago, nothing's been changed for quite some time. 1) Would it be safe to just remove the xs:biginteger? 2) Could you check this schema for any other types that should be there? > Confusing data type "integer" and "int" > --------------------------------------- > > Key: TEIIDDES-2256 > URL: https://issues.jboss.org/browse/TEIIDDES-2256 > Project: Teiid Designer > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Ramesh Reddy > > I understand that > "integer" maps to "xs:biginteger" > "int" maps "xs:long" > How they are confusing when there is already one available for biginteger. Also the Table creation wizard does not provide option to to select "int". When user chooses "integer" it often is "int". > This confusion needs to be resolved. IMO "integer" can be removed, however I am not sure how it effects data type system -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2256) Confusing data type "integer" and "int"

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2256?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2256: ---------------------------------------- Our design-time types are defined here: https://github.com/Teiid-Designer/teiid-designer/blob/master/plugins/org.... Except for adding *varbinary* 2 years ago, nothing's been changed for quite some time. 1) Would it be safe to just remove the xs:biginteger? 2) Could you check this schema for any other types that should be there? > Confusing data type "integer" and "int" > --------------------------------------- > > Key: TEIIDDES-2256 > URL: https://issues.jboss.org/browse/TEIIDDES-2256 > Project: Teiid Designer > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Ramesh Reddy > > I understand that > "integer" maps to "xs:biginteger" > "int" maps "xs:long" > How they are confusing when there is already one available for biginteger. Also the Table creation wizard does not provide option to to select "int". When user chooses "integer" it often is "int". > This confusion needs to be resolved. IMO "integer" can be removed, however I am not sure how it effects data type system -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2256) Confusing data type "integer" and "int"

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2256?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-2256: ------------------------------------------ Maybe I'm confused, but there shouldn't be anything called xs:biginteger. The xsd to Teiid mapping would be: xs:integer -> biginteger xs:int -> integer xs:long -> long > Confusing data type "integer" and "int" > --------------------------------------- > > Key: TEIIDDES-2256 > URL: https://issues.jboss.org/browse/TEIIDDES-2256 > Project: Teiid Designer > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Ramesh Reddy > > I understand that > "integer" maps to "xs:biginteger" > "int" maps "xs:long" > How they are confusing when there is already one available for biginteger. Also the Table creation wizard does not provide option to to select "int". When user chooses "integer" it often is "int". > This confusion needs to be resolved. IMO "integer" can be removed, however I am not sure how it effects data type system -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2255) Creating VDBs in JBDS Teiid Designer give "Unparseable Date" exceptions

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2255?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2255: ----------------------------------- Fix Version/s: 8.6 8.5.1 Assignee: Barry LaFond > Creating VDBs in JBDS Teiid Designer give "Unparseable Date" exceptions > ----------------------------------------------------------------------- > > Key: TEIIDDES-2255 > URL: https://issues.jboss.org/browse/TEIIDDES-2255 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Editors > Affects Versions: 8.3, 8.4 > Environment: JVM's local is not English (ex. ja) > Reporter: hisao furuichi > Assignee: Barry LaFond > Fix For: 8.6, 8.5.1 > > > If a local for jvm is not English, user can not create a VDB in the Teiid Designer. The Designer keeps coming back with the exception: > {noformat} > Unparseable date: "Mon Jun 23 16:43:40 CEST 2014" > {noformat} > Additional info: > In org.teiid.designer.vdb.Vdb.java, SimpleDateFormat is instantiated without setting a local at Line 308(tag 8.3.3). I think following code will solve this issue. > {noformat} > SimpleDateFormat format = new SimpleDateFormat("EEE MMM dd HH:mm:ss zzz yyyy", java.util.Locale.ENGLISH); > {noformat} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2257) Create VDB DataSource Dialog Enhancements

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2257?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2257: ----------------------------------- Fix Version/s: 8.6 8.5.1 Assignee: Barry LaFond > Create VDB DataSource Dialog Enhancements > ----------------------------------------- > > Key: TEIIDDES-2257 > URL: https://issues.jboss.org/browse/TEIIDDES-2257 > Project: Teiid Designer > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Usability > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Fix For: 8.6, 8.5.1 > > Attachments: create-relational-native-query-procedure-result-set-panel.png, ds.png > > > 1) The dialog shows "OK" and "Cancel" buttons, they need to be "yes" or "no" buttons. > 2) If the data source is already available in server, then do not ask the user if they want to create it again. > Even better is, ask on the vdb-explorer window to enter (pre-fill) the JNDI name, with a check-box to create or not, rather than asking at later time. No annoying pop-up dialog. > Plus Points: To be useful, provide right click on VDB in server panel and create a Data source. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2257) Create VDB DataSource Dialog Enhancements

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2257?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2257: ----------------------------------- Attachment: create-relational-native-query-procedure-result-set-panel.png FYI the *Create VDB Data Source* action to the VDB context menu in the server was added for 8.3 release. > Create VDB DataSource Dialog Enhancements > ----------------------------------------- > > Key: TEIIDDES-2257 > URL: https://issues.jboss.org/browse/TEIIDDES-2257 > Project: Teiid Designer > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Usability > Reporter: Ramesh Reddy > Attachments: create-relational-native-query-procedure-result-set-panel.png, ds.png > > > 1) The dialog shows "OK" and "Cancel" buttons, they need to be "yes" or "no" buttons. > 2) If the data source is already available in server, then do not ask the user if they want to create it again. > Even better is, ask on the vdb-explorer window to enter (pre-fill) the JNDI name, with a check-box to create or not, rather than asking at later time. No annoying pop-up dialog. > Plus Points: To be useful, provide right click on VDB in server panel and create a Data source. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues July 2014