Search options (Page 3 of 5)

Great update Parcel.

BUGFIXES AND ENHANCEMENTS
I would be happy to include your modification or bugfixes in the current 0.42. To do this,  I need to keep track of your contribution (except for the fixes posted on forum).

May be the simplest way would be to mark the code changes with something like

//------- edited by Parcel on dd-mm-yyyy
...code
// ------- end ----------------

What do you think about it ?

UTF8 and UTF16
I'm very concerned with utf8 or utf16 support, even if the component is good enougth for english or french...It could then be used by many others people.
I currently use old fashion Delphi4 to code sqlitepass so I'm missing unicodestrings and I would appreciate your help to turn the component utf compliant from D4 to D2008 and Lazarus/fpc...

Ok Parcel,

I changed the RangeCheck error in TSqlitePassBitArray and have to work on TSqlitePassDatabase.CreateDatabase qnd GetRecord

as soon as I have enough time....

Luc

Thanks a lot Parcel.

I check and include your fixes in the 0.42 release.

Hi Wolfy,

The good news is : Yes SqlitePass handles blobs. (Images, Memo, ...etc)
The bad news is : In current version (0.41), when using images, This only works with Delphi and bmp.

FPC and Lazarus handles Memo but I still have problems with the Lazarus TdbImage that doesn't display images yet. This fix is planned for futur releases but I don't think it will be ready for the next 0.42 as I have to post questions on lazarus forum...I need help too...

Anyway, for xp and Delphi

Dowload and install the demo program from my site
Run and open the demo database ...SQLitePass\Demo\Databases\ExpertPersonal_dbdemos.db3
Select the Table Biolife.
You should be able to display Fishes bmp and Memo, Clear, Import, Export it...etc

Here is the code used in demo program (It uses a classic TDbImage component) :

procedure TMainForm.BtLoadPictureFromFileClick(Sender: TObject);
begin
if OpenPictureDialog.Execute
  then begin
       Dataset.Edit;
       TBlobField(DbImage.Field).LoadFromFile(OpenPictureDialog.Filename);
       end;
end;

procedure TMainForm.BtClearPictureClick(Sender: TObject);
begin
Dataset.Edit;
DbImage.Field.Clear;
end;

procedure TMainForm.BtSavePictureToFileClick(Sender: TObject);
begin
If SavePictureDialog.Execute
  then TBlobField(DbImage.Field).SaveToFile(SavePictureDialog.Filename);
end;

Using classic BlobField should be ok with other kinds of large data.

I know documentation is not very usefull for now but the components are having to many changes rigth now.

Let me know if you still have problem so others users could share our experience.

Regards.

Luc

Parcel, This bug was already solved in next 0.42. The current implementation is :

procedure TSqlitePassDataset.LocateMoveToRecord;
begin
  FLocateMoveState:= grError;

  if FLocateFoundRecords.Count = 0
     then Exit;

  if (FLocateCurrentItem > -1) and (FLocateCurrentItem < FLocateFoundRecords.Count) then
     begin
     MoveBy(Integer(FLocateFoundRecords.Items[FLocateCurrentItem]) - PInteger(ActiveBuffer)^);
     if FLocateCurrentItem = 0
        then FLocateMoveState := grBOF
        else if FLocateCurrentItem = Pred(FLocateFoundRecords.Count)
                then FLocateMoveState := grEOF
                else FLocateMoveState := grOk;
     end;
end;

I let you catch some more bugs...

Thanks

Parcel,

Thanks for this bug fix. I didn't test it yet but...

The procedure TSqlitePassTranslator.IntegerToTimeText will be modified in the next release with :

...
Const
TimeDiv = 86400000; { 1000 / 60 / 60 / 24 }

var
....
TimeValue : TTime;

begin
 TimeValue := Value / TimeDiv;
 DecodeTime(TimeValue, Hour, Min, Sec, MSec);
...

Hi Tohang,

I don't know if someone else had the same problem compiling the package. The units you mentioned are old units from another project I started years ago. They are not used by Sqlitepass so you can find the reference(s) that point to them and remove it.

What is your developpement platform D4, lazarus, Winxp, Linux ?...

What package did you used to install ?

The current version is 0.41 ... Did you want to mean "hope 0.42 will be work well" ?

Regards.

Luc

Thanks for your database.

This setting works correctly (tested with 0.41 library)

As you can see here (if you cannot enlarge the picture, do a 'save as' with your browser) :

Ok, this is fixed in the 0.41

I will upload the new library by next week.

The TSqlitePassSelectStmt.BuildSchema retrieves tables names and fields names from the following sqlite functions :
     FieldName := SqliteDbv3_column_origin_name(StmtHandle, i);
     TableName := SqliteDbv3_column_table_name(StmtHandle, i);

I am using these functions because I don't have a built-in sql parser yet (planed for futur versions). The bad news : sometimes, sqlite returns an empty tablename. I think this is what happened with your query.

A possible work around would be to provide the correct table and field names directly in the buildschema function (replacing SqliteDbv3_column_origin_name(StmtHandle, i) with your own function that should return the table name...)

I'm already working on others changes in the TSqlitePassSelectStmt object so I don't think it will be for the next version.

I'm very interested in finding an answer to this problem. That will allow to use the component whithout the need to compile the sqlite library with SQLITE_ENABLE_COLUMN_METADATA.