On 3-10-2012 9:05, michael.vancann...@wisa.be wrote:
> On Tue, 2 Oct 2012, Reinier Olislagers wrote:
>
>> Hi list,
>>
>>
>> IBConn:TIBConnection;
>> ...
>> IBConn:=TIBConnection(FConn.ProxyConnection);
>> IBConn.UserName:=FConn.UserName;
>> IBConn.Password:=FConn.Password;
>> IBConn.DatabaseName:
On Tue, 2 Oct 2012, Reinier Olislagers wrote:
Hi list,
IBConn:TIBConnection;
...
IBConn:=TIBConnection(FConn.ProxyConnection);
IBConn.UserName:=FConn.UserName;
IBConn.Password:=FConn.Password;
IBConn.DatabaseName:=FConn.DatabaseName;
...
IBConn.CreateDB;
Is that the best/easiest way? Would
Hm, i see these ways:
1. Add CreateDB/DropDB methods to SQLConnector (like others methods,
CreateDB is virtual at TSQLConnection level):
procedure TSQLConnector.CreateDB;
begin
CheckProxy;
FProxy.CreateDB;
end;
2. Add getter for Proxy property:
function TSQLConnector.GetProxy: TSQLConnection
Hi list,
For a fpcunit database test listener I'm implementing multi-connector
support using TSQLConnector. This seems to work nicely.
If the Firebird connector is chosen and the hostname is empty, I assume
Firebird embedded is used and if not present, a database needs to be
created using .Create
