75 results found
-
Support TDataset.FieldOptions (AutoCreateMode) in Unidac
Please implement the support of AutoCreateMode in your components.
Further description:
http://docwiki.embarcadero.com/Libraries/Rio/en/Data.DB.TFieldOptions.AutoCreateModeWith this option it's possible to create calculated fields in design time and all other fields will be added automaticly on runtime.
3 votes -
TfrxUniDACComponents Suport For Lazarus
Looking in the "UniDAC\Demos\ThirdParty\FastReport\" folder, I found a component: "TfrxUniDACComponents", which integrates Unidac with FastReport for Delphi, but I didn't find it for Lazarus. I'm using Lazarus 2.2.6 and would like to know if it's possible to develop this component for Lazarus as well.
3 votes -
Use TMonitor instead T(RTL)CriticalSection
Since the latest delphi has resolved all the major bugs of TMonitor and it's stable it would be nice to use it instead of T(RTL)CriticalSection.
It's way more faster locking so more performance gains of UniDac and our apps.
You case you Defines to change the lock mechanism for older versions of Delphi.
3 votes -
Add "Inverse Null Sort" (f.e.: "IN") function to IndexFieldNames
As the "coInvertNullOrder" flag -for client side sorting the dataset- is already imlpemented for some of the providers, it would be nice to be able to control the default method how NULL values are sorted (comes as first or comes as last).
The best approach would be to be able to control this over f.e. with an "IN" postfix in the IndexFieldNames, per field.
Like: "SomeField DESC IN;OtherField ASC"
Thx.
3 votes -
Support out params in ANONYMOUS BLOCK for PostgreSQL
DO $block$ begin :c:=100; end; $block$
This works for Oracle, but not for PostgreSQL
3 votes -
dbmonitor
dbMonitor - Define in the application for each TUniConnection if it sends messages to dbMonitor or not.
3 votes -
dbMonitor and TUniQuery - final SQL without parameters
dbMonitor
Please add another tab next to the tabs "SQL, Parameters, Error, CallStack" e.g. "Final SQL" in which we would be able to see SQL query with real parameter values instead of parameter placeholders ":Param1, Param2,...".
Please show real value of MEMO fields (TEXT - PostgreSQL, BLOB SUBTYPE 1 - Firebird, etc.) in parameters tab instead something like <BLOB:xxx>.
For real BLOB types (BLOB SUBTYPE 0 or BINARY) you can leave <BLOB:xxx>
TUniquery
Please add some property (like FinalSQL) but with real parameter values instead of parameter placeholders ":Param1, :Param2,...", so we can see actual SQL when debugging from Delphi…
3 votes -
Native driver for Filemaker Server database
The only way to access a Filemaker Server database is via ODBC, which is not supported in iOS. There is a large installation of Filemaker databases out there, backed by Apple, and with the increasing market share of Mac, iPad and iPhone, it will likely gain in popularity.
3 votes -
Implement Support for Raspberry Pi plattaform using lazarus.
Implement support for Raspberry Pi and arm general Iot using lazarus. Im a lazarus user and rapsberry work exceleent with my app. Just need a stable dataaccess like unidac on raspberry pi.
3 votes -
Manually parse SQL for MBCS strings
Manually parse SQL for MBCS strings.
Latest UniDac MBCS specification is not full compatible with BDE/DBX(Delphi Ansi version).
and issue parse exception by mistake and macro function character at not ParamCheck.
and this exception is difficult to understand the cause.
(I have send details to support already)Please add the following property/Event.
- SkipParseSQL property
- OnBeforeParseSQL
- OnSQLParseError
3 votes -
Unified SQL: add function "dayoftheyear"
Please add the function dayoftheyear to the list of unified sql functions
3 votes -
dbMonitor shows string fields as <BLOB:19> Should show the actual data
dbMonitor, which is a great feature, shows any string values as <BLOB:19> instead of the actual data in that field. This might only apply to postgresql
3 votes -
Add functionality to allow compacting a Jet 4.0 (Access) database
Currently it is not possible to use UniDAC to compact an existing Jet database.
2 votes -
TUniLoader with Firebird - automaically calulate maximal value for RowsPerBatch
For Firebird the possible value for RowsPerBatch depends on the number of rows in the table because the maximal length of an SQL statement is 64KB.
For RowsPerBatch=0, UniDac should calculate the maximal possible value itself.2 votes -
Автогенерация InsertSQL, UpdateSQL
Я знаю, что у TUniQuery есть возможность сгенерировать доп. запрос на основе SelectSQL.
Но это неочевидно, в справке нет. Нет готовых методов.
Приходится открывать предварительно сам запрос, что есть не совсем правильно.[code] UniQuery1.Open;
UniQuery1.SQLUpdate.Text := TDBAccessUtils.SQLGenerator(UniQuery1).GenerateSQL(TDAParamsInfo.Create(TDAParamInfo) , _stUpdate, true);
UniQuery1.SQLRefresh.Text := TDBAccessUtils.SQLGenerator(UniQuery1).GenerateSQL(TDAParamsInfo.Create(TDAParamInfo) , _stRefresh, true);
[/code]
да и без UniQuery1.Open вываливается AV :(Было бы здорово, если бы было что-то вроде:
UniQuery1.GelerateAllSQLs.
UniQuery1.GelerateInsertSQL;
UniQuery1.GelerateUpdateSQL;
UniQuery1.GelerateDeleteSQL;
и т.д.
и без обязательного открытия набора данных.1 vote -
Expose low level access to data.
Sometimes it's required to read a lot of records from db server as fast as possible and collect it to dictionary etc. Even tough Unidac (at least with PostegreSQL) is fast, having tdataset, tfield in middle will slow down things a littlebit.
I'm looking to solutions like this pseudo level code
q.sql.text := 'select Barcode,price,name from table where ...';
q.open;
q.useOnlyeLowLevel := true; //disables mapping to fields.
while not q.eof do
begin
lean:= q.lowlevel.readString;
lPrice := q.lowlevel.readFloat;
lname := q.lowlevel.readString;
// do something with lean, lprice, lname
q.next;
end;
Of cource this could implemented with other type of solution.I'm…
1 vote -
TMyTable - Please add SORT function :-(
I'm cobnverting from ADO to MyDac...and the tables don't have a SORT function.
1 vote -
android
Connect to Firebird direct via Android and IOs without the need for a DB Client similar to PostgreSQL, Mysql, Redshift and Nexus.
1 vote -
The ability to create views with identical field names.
It will not take over the identical field names of a view. If multiple fields have the same name located in different sub-tables of this view.
1 vote -
Migration Wizard (Strip the .DB from tablenames if Paradox)
When converting from Paradox to SQLite, I ran into 2 problems.
1) the TableName.DB I used in paradox does NOT have a .DB ending in the actual tablename...
2) The data module where the "database1" was declared for the TUniConnection was not included in the files, and then the connections were not set to them. I had to open all the forms and remove the .db and set themI think that the Migration Wizard should handle those better...
1 vote
- Don't see your idea?