Zeoslib Portal

Code: Select all

\subsubsection{new connection parameter fb\_protocol}
\label{sec:Rev6_FirebirdInterbase_Changes_FBProtocol}

The new parameter "fb\_protocol" was introduced as a connection parameter.
With Firebird 3 this paramater switches Zeos to use url style connection strings.
This enables you to force the library to use xnet for connecting to the server, bypassing a local engine12.
This parameter also allows you to use the wnet (Named Pipes) protocol on older versions of Firebird and on Interbase.
For possible values of fb\_protocol see table \ref{tbl:Rev6_ValuesFbprotocol} on Page \pageref{tbl:Rev6_ValuesFbprotocol}.

\begin{table}
    \begin{tabular}{ p{1cm} p{13cm} }
    Value & Description \\ \hline
    inet & This will create a connection string to be used with TCP/IP. If the server name is empty, localhost will be used as the server name. \\ %\hline
    wnet & This will create a connection string to be used with named pipes. If the server name is empty, a connection to a local server will be created. \\ %\hline
    xnet & On Firebird 3 this will force the client library to use an xnet (shared memory) connection to a local server. On Interbase and Firebird 2.5 and below the embedded server cannot be forced to use xnet, while the regular client library will always use xnet in that case. The server name will be ignored with this setting. \\
    local & This value will try to do a local connection. This will only work with embedded servers. Regular client libraries will usually fall back into using xnet. \\
		\end{tabular}
    \caption{values for fb\char`_protocol}
    \label{tbl:Rev6_ValuesFbprotocol}
\end{table}

Code: Select all

\subsection{Date and Time format settings}
\label{sec:Rev4_GeneralChanges_DateAndTimeFormatSettings}
Zeos now supports specifying date and time format settings that will be used if Zeos doesn't know how to correctly format date and time settings for the DBMS to understand them.
This feature gets used with emulated parameters in ADO - if the FoxPro driver is used for example.
These new parameters can be set in the TZConnection.Properties property.
The format of these parameters conforms to the usual Delphi standards.
The following new parameters are supported:
\begin{itemize}
\item DateReadFormat
\item DateWriteFormat
\item DateDisplayFormat
\item TimeReadFormat
\item TimeWriteFormat
\item TimeDisplayFormat
\item DateTimeReadFormat
\item DateTimeWriteFormat
\item DateTimeDisplayFormat
\end{itemize}
The ReadFormat parameters decribe the date and time formats as the data\-base sends them to the application.
The WriteFormat parameters describe the date and time formats as the application should send them to the database.
The DisplayFormat settings are used for strings that are supplied by the application to Zeos.
These settings can be used to solve problems on the following drivers:
\begin{itemize}
\item dblib (FreeTDS, mssql, sybase)
\item postgresql
\item mysql (depending on parameter preferprepared, used if preferprepared is not set)
\item ado (emulated parameters, see \ref{sec:Rev4_DriverSpecificChanges_Ado} \nameref{sec:Rev4_DriverSpecificChanges_Ado}, Page \pageref{sec:Rev4_DriverSpecificChanges_Ado})
\end{itemize}

Code: Select all

const
  /// <summary>
  ///  Name of a user, same as <c>IZConnection.User</c> property
  /// </summary>
  /// <param name="TYPE"> STR </param>
  /// <param name="DBCs"> MySQL, Oracle </param>
  Prop_UID = 'username';

Code: Select all

  {**
   Password of a user, same as `IZConnection.Password` property
   @param TYPE = STR
   @param DBCs = MySQL, Oracle }
  Prop_Pass = 'password';

Code: Select all

  // Type: STR
  // Refer to MySql manual for details
  ConnProps_Datadir = MySQLProp_Datadir;
  // Type: STR
  // Path to library
  ConnProps_Library = MySQLProp_Library;

Code: Select all

//EH @ Fr0sT and aehimself
//just a proposal which is not related to the docs you guys are planning
//it would be nice to have a PropertyEditor possibility for the DataSet guys
//we could define each prop to a rercord. In initialization part of the
//PropertyEditor unit we could load them into "something"
//much smarter would be to define all records into an static record of TZProperty
//like TZPropertyArray = Array[0..x] of TZProperty = ( ...... add all of them )
//that way a PropertyEditor could access the array directly and we would never
//forget to add that prop to the Editor unit.. would the docs work for array elements too?
//It's just an Proposal
Type
  TZPropertyType = (
    ptEmpty,
    ptBool,
    ptInteger,
    ptString,
    ptBoolOrString);
const
  cProptertyTypeDesc: Array[TZPropertyType] of String = (
    'no value expected',
    'boolean expresson like ''Y''/''YES''/''T''/''TRUE''/''ON''/<>0 in any case to enable, any other',
    'any ordinal number',
    'any string value',
    'either BOOL expression or string value');
type
  PZProperty = ^TZProperty;
  TZProperty = Record
    _Type: TZPropertyType;
    Name: String;
    Porpose: String;
  End;

  TZServerProviders = set of TZServerProvider;
  TZConnProperty = record
    Prop: TZProperty;
    Providers: TZServerProviders;
  end;

const
  ProposalConst: TZProperty = (
    _Type: ptEmpty;
    //add Doc here ?
    Name: 'proposal';
    Porpose: 'do what you want');

const ZPropertiesArray: array[0..1] of TZProperty = (
  (
    _Type: ptEmpty;
    Name: 'proposal';
    Porpose: 'do what you want you have free hand, open your mind (% (:EH'),
  (
    _Type: ptBoolOrString;
    Name: 'Idea';
    Porpose: 'just an idea for the gui guys..... hope it helps, (:EH')
  );

Code: Select all

TZConnectionProperty = Class
 strict private
  _displayname: String;
  _propertyname: String;
  _help: String;
  _protocol: String;
 strict protected
  PropValue: String;
 public
  Constructor Create(inPropertyName, inDisplayName, inHelp, inProtocol: String); ReIntroduce; Virtual;
  Property DisplayName: String Read _displayname;
  Property PropertyName: String Read _propertyname;
  Property Help: String Read _help;
  Property Protocol: String Read _protocol;
  Property AsString: String Read PropValue;
 End;

 TZConnectionStringProperty = Class(TZConnectionProperty)
 public
  Property Value: String Read PropValue Write PropValue;
 End;

 TZConnectionIntegerProperty = Class(TZConnectionProperty)
 strict private
  Procedure SetValue(Const inValue: Integer);
  Function GetValue: Integer;
 public
  Constructor Create(inPropertyName, inDisplayName, inHelp, inProtocol: String); Override;
  Property Value: Integer Read GetValue Write SetValue;
 End;

 TZConnectionBooleanProperty = Class(TZConnectionProperty)
 strict private
  Procedure SetValue(Const inValue: Boolean);
  Function GetValue: Boolean;
 public
  Constructor Create(inPropertyName, inDisplayName, inHelp, inProtocol: String); Override;
  Property Value: Boolean Read GetValue Write SetValue;
 End;

Code: Select all

 TZConnectionPropertyClass = Class Of TZConnectionProperty;

 TZConnectionProperties = Class
 strict private
  _proplist: TObjectDictionary<String, TZConnectionProperty>;
  Function Add(inPropertyClass: TZConnectionPropertyClass; inPropertyName, inDisplayName, inHelp, inProtocol: String): TZConnectionProperty;
  Function GetItems(inPropertyName: String): TZConnectionProperty;
 public
  Constructor Create; ReIntroduce;
  Destructor Destroy; Override;
  Property Items[inPropertyName: String]: TZConnectionProperty Read GetItems; Default;
 End;

Code: Select all

 TConnProp = Record
  PropertyName: String;
  DisplayName: String;
  Help: String;
  HelpURL: String;
  ValidValues: String;
 End;

 PConnProp = ^TConnProp;