User Tools

Site Tools


overview

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
overview [2018/05/09 19:38] – [Command-line execution] dmitryoverview [2019/09/12 05:47] – added data sources in 3.9.5 dmitry
Line 2: Line 2:
  
 ==== Data Import ==== ==== Data Import ====
-In order to start transforming data in EasyMorph, all data subject to manipulations has to be imported into EasyMorph as tables. As of version 3.EasyMorph supports the following data sources:+In order to start transforming data in EasyMorph, all data subject to manipulations has to be imported into EasyMorph as tables. As of version 3.9.5 EasyMorph supports the following data sources:
   * Relational databases (Oracle, MS SQL Server, MySQL, PostgreSQL, SQLite)   * Relational databases (Oracle, MS SQL Server, MySQL, PostgreSQL, SQLite)
   * ODBC data sources (Oracle, MS SQL Server, MySQL, PostgreSQL, SQLite, Amazon Redshift, Vertica, SAP HANA, Apache Hive)   * ODBC data sources (Oracle, MS SQL Server, MySQL, PostgreSQL, SQLite, Amazon Redshift, Vertica, SAP HANA, Apache Hive)
Line 8: Line 8:
   * Text files with fixed with columns   * Text files with fixed with columns
   * Excel files (.xlsx, .xlsm, .xls)   * Excel files (.xlsx, .xlsm, .xls)
 +  * Google Sheets
 +  * SharePoint lists
   * Qlik data files (.qvd)   * Qlik data files (.qvd)
   * SAS files (.sas7bdat)   * SAS files (.sas7bdat)
   * SPSS/PSPP files (.sav)   * SPSS/PSPP files (.sav)
 +  * EasyMorph datasets (.dset)
  
 Once tables are loaded into EasyMorph they can further be modified using transformations that are applied one after another. Once tables are loaded into EasyMorph they can further be modified using transformations that are applied one after another.
Line 30: Line 33:
 Actions are executed consequently, step-by-step. One action is one step. Every action is applied to the result (output) of previous action. Therefore sequence of actions is important. The same actions in different order would usually produce a different result (although not always). Actions are executed consequently, step-by-step. One action is one step. Every action is applied to the result (output) of previous action. Therefore sequence of actions is important. The same actions in different order would usually produce a different result (although not always).
  
-Final state (or result) of a table is the result of all actions of this table applied consequently, one after another.+The final state (or result) of a table is the result of all actions of this table applied consequently, one after another.
  
 Some actions (e.g. [[transformations:append|Append Table]]) require another table. These actions have two inputs -- one input is the result of previous action in the same table and the other input is the final state (i.e. the result of last action) of the other table. Some actions (e.g. [[transformations:append|Append Table]]) require another table. These actions have two inputs -- one input is the result of previous action in the same table and the other input is the final state (i.e. the result of last action) of the other table.
overview.txt · Last modified: 2022/07/22 04:36 by dmitry

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki