Hi,
Thanks Anjana and Lahiru for the suggestions. Please find below the found
observations.
Following are the DB actions.
- DB creation (IF NOT EXIST)
- Table creation (IF NOT EXIST)
- Insert data to table
- update data to table
Since all the DBMS's are using same DDL and DML query formats we
Hi,
please note above varchar length will be given as default. eg:-
varchar(250).
Regards,
damith.
On Mon, Dec 1, 2014 at 5:10 PM, Damith Wickramasinghe dami...@wso2.com
wrote:
Hi,
Thanks Anjana and Lahiru for the suggestions. Please find below the found
observations.
Following are the
Hi Damith,
I'm personally biased towards just using the whole queries in the XML,
where we may get some subtle changes in queries that may not be possible
with your parameterized approach. For example, in MySQL, you can give the
storage table engine as a part in the DDL query. Likewise, there
Hi Damitha,
As Anjana suggested, separating only the data types would lead to some
confusions. Furthermore might, sometimes lead to not using a specific
database system to it's fullest potential. For example, given that there
are a huge amount of built-in functions in MSSQL we might be able to
Hi,
Thanks Anjana and Akalanka for the suggestions. @Anjana As per the off-line
discussion we had, I will add the necessary for the implementation.
Regards,
Damith.
On Mon, Dec 1, 2014 at 5:49 PM, Akalanka Pagoda Arachchi darsha...@wso2.com
wrote:
Hi Damitha,
As Anjana suggested,
The main issue is that we have to solve is the ability to handle different
syntax.
Please have a look at DSS and Hive Table definitions (from BAM) they may
help.
Suho
On Fri, Nov 28, 2014 at 4:49 PM, Damith Wickramasinghe dami...@wso2.com
wrote:
Hi,
Currently we have the support only for
Thanks, I will look on those and update the thread.
Regards,
Damith.
On Fri, Nov 28, 2014 at 5:23 PM, Sriskandarajah Suhothayan s...@wso2.com
wrote:
The main issue is that we have to solve is the ability to handle different
syntax.
Please have a look at DSS and Hive Table definitions (from
Hi,
An approach we can follow is, to give query templates from a configuration
file, so we don't have to embed/hard-code any queries in the code. I'm
using this approach in our new BAM RDBMS connector implementation, where
I'm going to use an XML configuration to have separate sections for each
Hi,
Maintenance wise it's nice to keep queries in separate XML.
And I think it's better to keep all the generic queries in a one section of
the XML and keep DBMS specific queries in separate sections. So you don't
need to rewrite common queries for each type. Also better to consider MS
SQL Server
