Default Settings: Connection Tab

The "Connection" tab of default settings is where the database connection string is entered and the language mapping, database target, and user meta-data file are selected.

Database Connection

The first step is to connect to the database that you wish to operate with. Select the Database type then enter the connection string. Below is a list of the databases supported by MyGeneration and the required driver information.
Database Driver Sample Connection String Driver Included?
Firebird Firebird Manager Driver Database=C:\firebird\EMPLOYEE.GDB;User=SYSDBA;Password=wow;Dialect=3;Server=localhost Yes
IBM DB2 IBM OLE DB Provider for DB2 Servers Provider=IBMDADB2.1;Password=sa;User ID=DB2Admin;Data Source=MyMeta;Persist Security Info=True No
Interbase Firebird Manager Driver Database=C:\interbase\EMPLOYEE.GDB;User=SYSDBA;Password=wow;Dialect=3;Server=localhost Yes
Microsoft Access Microsoft Jet 4.0 OLE DB Provider Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\access\newnorthwind.mdb;User Id=;Password= No
Microsoft SQL Server Microsoft OLE DB Provider for SQL Server Provider=SQLOLEDB.1;Persist Security Info=False;User ID=sa;Initial Catalog=Northwind;Data Source=localhost No
MySQL MySQL.OLEDB Provider Provider=MySQLProv;Persist Security Info=True;Data Source=test;UID=griffo;PWD=;PORT=3306 No
MySQL2 MySQL Connector/Net Database=Test;Data Source=Griffo;User Id=anonymous; No
Oracle Oracle Provider for OLEDB Provider=OraOLEDB.Oracle.1;Password=sa;Persist Security Info=True;User ID=GRIFFO;Data Source=dbMeta No
PostgreSQL Npgsql Server=127.0.0.1;Port=5432;User Id=joe;Password=secret;Database=joedata; Yes
SQLite SQLite.NET Data Source=database.db;New=False;Compress=True;Synchronous=Off Yes
VistaDB VistaDB Data Provider DataSource=C:\Program Files\VistaDB 2.0\Data\Northwind.vdb;Cypher= None;Password= ;Exclusive=False;Readonly=False; No
Advantage Advantage .NET Data Provider Provider=Advantage.OLEDB.1;Password="";User ID=AdsSys;Data Source=C:\Program Files\Extended Systems\Advantage\Help\examples\aep_tutorial\task1;Initial Catalog=aep_tutorial.add;Persist Security Info=True;Advantage Server Type=ADS_LOCAL_SERVER;Trim Trailing Spaces=TRUE No
IBM iSeries IBM iSeries Client Access Drivers PROVIDER=IBMDA400; DATA SOURCE=MY_SYSTEM_NAME;USER ID=myUserName;PASSWORD=myPwd;DEFAULT COLLECTION=MY_LIBRARY; No
VistaDB 3.x VistaDB 3.x CTP Provider=Data Source=C:\Program Files\VistaDB 3.0 CTP\Data\Northwind.vdb3;OpenMode=NonexclusiveReadOnly No
Delimited Text Microsoft Jet OleDb Drivers Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\TxtFilesFolder\;Extended Properties='text;HDR=Yes;FMT=Delimited' Yes

Language

If you are generating code to access a database from Java, C#, or another language, you will want to select the correct data-type mapping for the specified language. The language mappings associate database types with language types. For example, with SQLServer and C#, the "bit" type maps to the "boolean" type. If you wish to add new language mappings, you can add them to the "Languages.xml" file located in the Settings folder. Language Mappings can most easily be edited through the MyMeta browser and Language Mappings form.

Database Target

Depending on the technology you're using, there may be a mapping between the database type and the driver type. With SQLServer, there may be many different drivers that support data access into Java or C#. In C#, the if you choose to use the SqlServer managed driver that microsoft provides, the "binary" type maps to "SqlDbType.Binary". Database Targets can be edited through the MyMeta browser and the DBTargets form or directly edited in the "DbTargets.xml" file.

User Meta-Data

User meta-data contains aliases of database, table, and column names, along with custom key-value pairs that can be added at the table and column level of the MyMeta API. This is useful when generating code with readable class, property, and method names. for example, a table with the name "TBL_USER_RX_S001" would probably be aliased as "User" in a generated class. User meta-data can be edited through the MyMeta browser and the User Meta-Data form or directly edited in the "UserMetaData.xml" file.