Why don't you use a store procedure for this ?
You can either CRON a call to this stored procedure or even call this stored procedure from your software.
Search found 451 matches
- Thu 22 Sep 2016 15:49
- Forum: Universal Data Access Components
- Topic: Not an error but help required
- Replies: 3
- Views: 1211
- Tue 13 Sep 2016 09:21
- Forum: Universal Data Access Components
- Topic: UniDAC 6.4.14 / Custom dialog form issue
- Replies: 2
- Views: 1203
Re: UniDAC 6.4.14 / Custom dialog form issue
I've found....
My application is a VCL one.
I've inadvertently added an FMX.Forms in one of my unit.
Because of this, Classes.RegisterClass failed without throwing an exception....
Removing FMX.Forms solved my problem.
My application is a VCL one.
I've inadvertently added an FMX.Forms in one of my unit.
Because of this, Classes.RegisterClass failed without throwing an exception....
Removing FMX.Forms solved my problem.
- Tue 13 Sep 2016 08:16
- Forum: Universal Data Access Components
- Topic: UniDAC 6.4.14 / Custom dialog form issue
- Replies: 2
- Views: 1203
UniDAC 6.4.14 / Custom dialog form issue
Hello,
I've a strange issue as I can't register my custom dialog form anymore.
TfmConnectiondialog is correctly registered but GetClass('TfmConnectiondialog') always return nil
And connection DialogClass is correctly set :
UniDAC demo is working fine... Go figure ?
I've a strange issue as I can't register my custom dialog form anymore.
Code: Select all
'first chance' Exception at $74B996C2. exception class EClassNotFound with message 'TfmConnectiondialog class not found'.
Code: Select all
Initialization
If GetClass('TfmConnectiondialog') = Nil Then
Classes.RegisterClass(TfmConnectiondialog);
Code: Select all
UniConnectDialog1.DialogClass := 'TfmConnectiondialog';
- Mon 04 Jul 2016 12:43
- Forum: Universal Data Access Components
- Topic: [6.3.13/PostgreSQL]Connection failed when port is set to 0
- Replies: 3
- Views: 790
Re: [6.3.13/PostgreSQL]Connection failed when port is set to 0
is there any ETA ?
- Mon 04 Jul 2016 12:27
- Forum: Universal Data Access Components
- Topic: [6.3.13/PostgreSQL]Connection failed when port is set to 0
- Replies: 3
- Views: 790
[6.3.13/PostgreSQL]Connection failed when port is set to 0
Hello,
Starting 6.3.13, postgreSQL connection is failing when letting it's default port value to 0.
This used to works on all previous release.
Setting explicitly the port to 5432 solves the problem.
Starting 6.3.13, postgreSQL connection is failing when letting it's default port value to 0.
This used to works on all previous release.
Setting explicitly the port to 5432 solves the problem.
- Mon 30 May 2016 17:42
- Forum: Universal Data Access Components
- Topic: Android : bulk insert leads to 'ESQLiteError' with message 'disk I/O error'.
- Replies: 2
- Views: 1424
Android : bulk insert leads to 'ESQLiteError' with message 'disk I/O error'.
Hello,
Bulk insert leads to 'ESQLiteError' with message 'disk I/O error'. This is specially happening when inserting a large amout of data (107 000 inserts).
I've tried to insert with and without a transaction but nothing change.
When no transaction is used, I'm still getting error message (after the disk I/O error) 'cannot rollback - no transaction is active'.
Bulk insert leads to 'ESQLiteError' with message 'disk I/O error'. This is specially happening when inserting a large amout of data (107 000 inserts).
I've tried to insert with and without a transaction but nothing change.
When no transaction is used, I'm still getting error message (after the disk I/O error) 'cannot rollback - no transaction is active'.
- Fri 20 May 2016 14:23
- Forum: Universal Data Access Components
- Topic: 6.3.12 / batch operation issue "Array index out of range"
- Replies: 3
- Views: 2168
Re: 6.3.12 / batch operation issue "Array index out of range"
I've changed valueCount to 1 and problem still persists
- Fri 20 May 2016 12:20
- Forum: Universal Data Access Components
- Topic: 6.3.12 / batch operation issue "Array index out of range"
- Replies: 3
- Views: 2168
6.3.12 / batch operation issue "Array index out of range"
I'm getting "Array index out of range" when running such code. It looks like array used for batch updates ins't updated when SQL property is changed.
Code: Select all
try
for AMember in x.A['articles'] do
begin
Qry.SQL.Text := sqlStockArticlesDelete;
Qry.Params[0].DataType := ftString;
Qry.Params[1].DataType := ftString;
Qry.Params[0].AsString := AMember.AsObject.S['gencod_art'];
Qry.Params[1].AsString := AMember.AsObject.S['code_art'];
Qry.Execute; <==== error occurs on the 2nd loop. Looks like array isn't initialized after changing the SQL property.
Qry.SQL.Text := sqlStockArticlesInsert;
Qry.Params[0].DataType := ftString;
Qry.Params[1].DataType := ftString;
Qry.Params[2].DataType := ftString;
Qry.Params[3].DataType := ftInteger;
Qry.Params[4].DataType := ftFloat;
Qry.Params[0].AsString := AMember.AsObject.S['lib_art'];
Qry.Params[1].AsString := AMember.AsObject.S['gencod_art'];
Qry.Params[2].AsString := AMember.AsObject.S['code_art'];
Qry.Params[3].AsInteger := AMember.AsObject.i['colisage'];
Qry.Params[4].asfloat := AMember.AsObject.f['stock'];
Qry.Execute;
if AMember.AsObject.A['artDetail'].Length >= 1 then
begin
Qry.SQL.Text := sqlStockArticlesDetailInsert;
Qry.Params[0].DataType := ftString;
Qry.Params[1].DataType := ftString;
Qry.Params[2].DataType := ftString;
Qry.Params[3].DataType := ftString;
Qry.Params[4].DataType := ftString;
Qry.Params[5].DataType := ftInteger;
Qry.Params.ValueCount := AMember.AsObject.A['artDetail'].Length;
for i := 0 to Qry.Params.ValueCount - 1 do
begin
Qry.Params[0][i].AsString := AMember.AsObject.S['gencod_art'];
Qry.Params[1][i].AsString := AMember.AsObject.S['code_art'];
Qry.Params[2][i].AsString := AMember.AsObject.A['artDetail'].O[i].S
['gencod'];
Qry.Params[3][i].AsString := AMember.AsObject.A['artDetail'].O[i].S
['couleur'];
Qry.Params[4][i].AsString := AMember.AsObject.A['artDetail'].O[i].S
['taille'];
Qry.Params[5][i].AsInteger := AMember.AsObject.A['artDetail'].O[i].i
['nb_pcs'];
end;
Qry.Execute(Qry.Params.ValueCount);
end;
end;
- Wed 27 Apr 2016 13:18
- Forum: Universal Data Access Components
- Topic: [6.3.11/Postgresql] EAccessViolation when connecting
- Replies: 5
- Views: 3065
- Tue 26 Apr 2016 06:55
- Forum: Universal Data Access Components
- Topic: [6.3.11/Postgresql] EAccessViolation when connecting
- Replies: 5
- Views: 3065
Re: [6.3.11/Postgresql] EAccessViolation when connecting
Exception is raised when setting specific options to
Is there a workaround ? This is a serious issue !
Code: Select all
'PostgreSQL.UseUnicode=True'
- Tue 26 Apr 2016 06:45
- Forum: Universal Data Access Components
- Topic: [6.3.11/Postgresql] EAccessViolation when connecting
- Replies: 5
- Views: 3065
Re: [6.3.11/Postgresql] EAccessViolation when connecting
This is also happening on empty project.
Should I send you a demo project ?
Should I send you a demo project ?
- Tue 26 Apr 2016 05:51
- Forum: Universal Data Access Components
- Topic: [6.3.11/Postgresql] EAccessViolation when connecting
- Replies: 5
- Views: 3065
[6.3.11/Postgresql] EAccessViolation when connecting
Hello,
I have an issue with latest version. My connection code haven't changed for years.
At design time, if I try to connect, i'm getting an EAccessViolation.
At runtime FConnectDialog.Connection.PerformConnect(FRetry) is throwing EAccessViolation.
Any ideas ?
My objects :
Callstack
I have an issue with latest version. My connection code haven't changed for years.
At design time, if I try to connect, i'm getting an EAccessViolation.
At runtime FConnectDialog.Connection.PerformConnect(FRetry) is throwing EAccessViolation.
Any ideas ?
My objects :
Code: Select all
object mainconnection: TUniConnection
ProviderName = 'PostgreSQL'
Database = 'xxx'
SpecificOptions.Strings = (
'PostgreSQL.ApplicationName=myCRM'
'PostgreSQL.Schema=public'
'PostgreSQL.UseUnicode=True')
Options.DisconnectedMode = True
Options.KeepDesignConnected = False
Options.LocalFailover = True
Username = 'xxx'
Server = 'xxx'
ConnectDialog = UniConnectDialog1
AfterConnect = mainconnectionAfterConnect
AfterDisconnect = mainconnectionAfterDisconnect
Left = 64
Top = 56
EncryptedPassword = 'xxx'
end
object UniConnectDialog1: TUniConnectDialog
DatabaseLabel = 'Base de donnees'
PortLabel = 'Port'
ProviderLabel = 'Fournisseur'
DialogClass = 'TfmConnectiondialog'
Caption = 'Ouverture de session'
UsernameLabel = 'Nom utilisateur'
PasswordLabel = 'Mot de passe'
ServerLabel = 'Serveur'
ConnectButton = 'Ok'
CancelButton = 'Annuler'
LabelSet = lsFrench
Left = 112
Top = 56
end
object UniSQLMonitor1: TUniSQLMonitor
Active = False
Options = [moDialog, moSQLMonitor, moCustom]
Left = 176
Top = 56
end
Code: Select all
callstack crc : $3a8928fd, $f10615ef, $4d43223a
exception number : 1
exception class : EAccessViolation
exception message : Violation d'accès à l'adresse 30E99EA8 dans le module 'pgprovider230.bpl'. Lecture de l'adresse 00000054.
main thread ($1ac8):
30e99ea8 +000 pgprovider230.bpl Pgsqlprotocoluni TPgSQLProtocol.SetUseUnicode
30eba24b +173 pgprovider230.bpl Pgclassesuni TPgSQLConnection.SetProp
13bd765d +161 unidac230.bpl Uniprovider TOptionsList.ImportOptions
13bd5b28 +030 unidac230.bpl Uniprovider TUniProvider.SetObjectProps
30ed1fe5 +0c5 pgprovider230.bpl Postgresqluniprovider TPostgreSQLUniProvider.SetObjectProps
13bce0e6 +33a unidac230.bpl Uni TUniConnection.CreateIConnection
139567be +03a dac230.bpl Dbaccess TCustomDAConnection.DoConnect
13bce39f +02f unidac230.bpl Uni TUniConnection.DoConnect
13956bbb +037 dac230.bpl Dbaccess TCustomDAConnection.PerformConnect
13c12a68 +184 unidacvcl230.bpl Uniconnectform TUniConnectForm.DoConnect
13c130ee +002 unidacvcl230.bpl Uniconnectform TUniConnectForm.btConnectClick
5099376b +073 vcl230.bpl Vcl.Controls 7365 +9 TControl.Click
509b8942 +01e vcl230.bpl Vcl.StdCtrls 5327 +3 TCustomButton.Click
509b94a8 +050 vcl230.bpl Vcl.StdCtrls 5798 +6 TCustomButton.CMDialogKey
509931fd +2bd vcl230.bpl Vcl.Controls 7249 +91 TControl.WndProc
50997d3d +5e9 vcl230.bpl Vcl.Controls 10079 +158 TWinControl.WndProc
509b85ec +06c vcl230.bpl Vcl.StdCtrls 5164 +13 TButtonControl.WndProc
50996515 +02d vcl230.bpl Vcl.Controls 9195 +3 TWinControl.Broadcast
50999e9c +000 vcl230.bpl Vcl.Controls 11487 +0 TWinControl.CMDialogKey
50ad71ca +092 vcl230.bpl Vcl.Forms 6741 +26 TCustomForm.CMDialogKey
509931fd +2bd vcl230.bpl Vcl.Controls 7249 +91 TControl.WndProc
50997d3d +5e9 vcl230.bpl Vcl.Controls 10079 +158 TWinControl.WndProc
50ad3514 +62c vcl230.bpl Vcl.Forms 4459 +206 TCustomForm.WndProc
50992e38 +024 vcl230.bpl Vcl.Controls 7027 +10 TControl.Perform
5099a32d +0d1 vcl230.bpl Vcl.Controls 11751 +23 TWinControl.CNKeyDown
509931fd +2bd vcl230.bpl Vcl.Controls 7249 +91 TControl.WndProc
50997d3d +5e9 vcl230.bpl Vcl.Controls 10079 +158 TWinControl.WndProc
5099735c +02c vcl230.bpl Vcl.Controls 9786 +3 TWinControl.MainWndProc
50172214 +014 rtl230.bpl System.Classes 16886 +8 StdWndProc
776e8e54 +034 ntdll.dll KiUserCallbackDispatcher
762a5ede +13e user32.dll SendMessageW
50adc89c +084 vcl230.bpl Vcl.Forms 10351 +25 TApplication.IsKeyMsg
50adcb4b +0cf vcl230.bpl Vcl.Forms 10437 +17 TApplication.ProcessMessage
50adcbb2 +00a vcl230.bpl Vcl.Forms 10473 +1 TApplication.HandleMessage
50ad80ca +1aa vcl230.bpl Vcl.Forms 7218 +33 TCustomForm.ShowModal
13a62e11 +06d dacvcl230.bpl Dacvcl ShowConnectForm
139745af +237 dac230.bpl Dbaccess TCustomConnectDialog.Execute
13c14897 +067 unidacvcl230.bpl Unidacvcl TUniConnectDialog.Execute
13956b51 +009 dac230.bpl Dbaccess TCustomDAConnection.Connect
13956a6f +06b dac230.bpl Dbaccess TCustomDAConnection.InternalConnect
1395fe80 +088 dac230.bpl Dbaccess TCustomDADataSet.BeginConnection
13bd0f22 +006 unidac230.bpl Uni TCustomUniDataSet.BeginConnection
13960e05 +07d dac230.bpl Dbaccess TCustomDADataSet.OpenCursor
13bd112b +027 unidac230.bpl Uni TCustomUniDataSet.OpenCursor
5106f72d +055 dbrtl230.bpl Data.DB 12470 +12 TDataSet.SetActive
13960d75 +03d dac230.bpl Dbaccess TCustomDADataSet.SetActive
5106f2a3 +033 dbrtl230.bpl Data.DB 12313 +3 TDataSet.Loaded
1395fd6e +022 dac230.bpl Dbaccess TCustomDADataSet.Loaded
501554b7 +02b rtl230.bpl System.Classes 4094 +3 NotifyGlobalLoading
211bb2bc +09c designide230.bpl ComponentDesigner 2322 +10 TComponentRoot.CreateFromStream
211bb003 +28b designide230.bpl ComponentDesigner 2272 +37 TComponentRoot.Create
524a1f3f +05b vcldesigner230.bpl VCLFormDesigner 1484 +3 TVCLFormDesigner.CreateRoot
21e44af8 +478 delphicoreide230.bpl DelphiModule 635 +68 TPascalCodeMgrModHandler.SetupSourceModules
21e44442 +05a delphicoreide230.bpl DelphiModule 518 +5 TPascalCodeMgrModHandler.Create
21e4c04d +06d delphicoreide230.bpl DelphiModule 3020 +6 TPascalGauntletHandler.AttachHandler
20881569 +039 coreide230.bpl DocModul 3211 +4 TModuleHandlerGauntlet.RunGauntlet
2087c991 +01d coreide230.bpl DocModul 949 +1 TDocModule.AfterConstruction
206aa76f +037 coreide230.bpl SourceModule 781 +3 TSourceModule.AfterConstruction
5005fef1 +01d rtl230.bpl System 17548 +2 @AfterConstruction
2087c340 +12c coreide230.bpl DocModul 806 +35 TFilterList.OpenFile
509931fd +2bd vcl230.bpl Vcl.Controls 7249 +91 TControl.WndProc
5005f898 +04c rtl230.bpl System 16559 +8 TObject.GetInterface
500671ff +00f rtl230.bpl System 37518 +1 TInterfacedObject.QueryInterface
501afd5e +002 rtl230.bpl System.SyncObjs 1063 +0 TCriticalSection.Leave
20880525 +125 coreide230.bpl DocModul 2693 +28 TCodeIDocModule.QueryInterface
50067110 +010 rtl230.bpl System 36557 +10 @IntfClear
20880542 +142 coreide230.bpl DocModul 2696 +31 TCodeIDocModule.QueryInterface
206133be +01a coreide230.bpl ProjectModule 2906 +0 TCustomCodeIProject.QueryInterface
21da9b1e +056 delphicoreide230.bpl BaseDelphiProject 1240 +3 TBaseDelphiProject.OpenModule
2061279c +014 coreide230.bpl ProjectModule 2636 +1 TCustomCodeIProject.OpenModule
211bd1a9 +081 designide230.bpl ComponentDesigner 3083 +5 TComponentRoot.LoadDependentModules
211bb040 +2c8 designide230.bpl ComponentDesigner 2279 +44 TComponentRoot.Create
524a1f3f +05b vcldesigner230.bpl VCLFormDesigner 1484 +3 TVCLFormDesigner.CreateRoot
21e44af8 +478 delphicoreide230.bpl DelphiModule 635 +68 TPascalCodeMgrModHandler.SetupSourceModules
21e44442 +05a delphicoreide230.bpl DelphiModule 518 +5 TPascalCodeMgrModHandler.Create
21e4c04d +06d delphicoreide230.bpl DelphiModule 3020 +6 TPascalGauntletHandler.AttachHandler
20881569 +039 coreide230.bpl DocModul 3211 +4 TModuleHandlerGauntlet.RunGauntlet
2087c991 +01d coreide230.bpl DocModul 949 +1 TDocModule.AfterConstruction
206aa76f +037 coreide230.bpl SourceModule 781 +3 TSourceModule.AfterConstruction
5005fef1 +01d rtl230.bpl System 17548 +2 @AfterConstruction
2087c340 +12c coreide230.bpl DocModul 806 +35 TFilterList.OpenFile
76a79dc6 +086 oleaut32.dll SysFreeString
50067110 +010 rtl230.bpl System 36557 +10 @IntfClear
0e2b314d +0ed projpageide230.bpl ProjectPageOptions 117 +14 FindNode
21e354e1 +01d delphicoreide230.bpl PasMgr 11083 +2 TPascalProjectUpdater.FindUsesEntry
204e2fa2 +06a coreide230.bpl Updaters 992 +7 GetMainFormNameImpl
21e33c0a +01e delphicoreide230.bpl PasMgr 10552 +2 TPascalProjectUpdater.GetMainFormName
21da8d91 +041 delphicoreide230.bpl BaseDelphiProject 983 +5 TBaseDelphiProject.DisplayProject
20613364 +000 coreide230.bpl ProjectModule 2891 +0 TCustomCodeIProject.DisplayProject
206aee5e +08e coreide230.bpl ProjectFileUtils 505 +22 ShowProject
208815e2 +012 coreide230.bpl DocModul 3226 +0 TFileOpenHandler.FileOpen
2087c340 +12c coreide230.bpl DocModul 806 +35 TFilterList.OpenFile
206a5d39 +041 coreide230.bpl FileHist 195 +6 TClosedFile.ReOpen
50ac0c6a +0aa vcl230.bpl Vcl.Menus 2539 +19 TMenuItem.Click
50ac2300 +018 vcl230.bpl Vcl.Menus 3461 +5 TMenu.DispatchCommand
50ac3572 +082 vcl230.bpl Vcl.Menus 4622 +4 TPopupList.WndProc
50ac34c1 +01d vcl230.bpl Vcl.Menus 4597 +2 TPopupList.MainWndProc
50172214 +014 rtl230.bpl System.Classes 16886 +8 StdWndProc
762a62fb +00b user32.dll DispatchMessageW
50adcb6f +0f3 vcl230.bpl Vcl.Forms 10443 +23 TApplication.ProcessMessage
50adcbb2 +00a vcl230.bpl Vcl.Forms 10473 +1 TApplication.HandleMessage
50adcee5 +0c9 vcl230.bpl Vcl.Forms 10611 +26 TApplication.Run
775a38f2 +022 KERNEL32.DLL BaseThreadInitThunk
- Wed 30 Mar 2016 15:58
- Forum: Universal Data Access Components
- Topic: Backups issues with accentuated characters
- Replies: 9
- Views: 1341
Re: Backups issues with accentuated characters
Please check your email box. You'll find a correct dump.
- Wed 23 Mar 2016 18:55
- Forum: Universal Data Access Components
- Topic: UniDAC on Lazarus / WinCE
- Replies: 1
- Views: 860
UniDAC on Lazarus / WinCE
Hello,
Will you consider to add WinCE support on Lazarus ?
BR
Will you consider to add WinCE support on Lazarus ?
BR
- Wed 23 Mar 2016 09:52
- Forum: Universal Data Access Components
- Topic: Backups issues with accentuated characters
- Replies: 9
- Views: 1341
Re: Backups issues with accentuated characters
I've sent you SQL dump + screenshots + demo project reproducing this.