I have uploaded v 1.6 of sqlite3Explorer (www.singular.gr/sqlite). It has some minor bug fixes and enhancements, plus support for REGEXP operator. Sqlite3Explorer has had regular expression support for a long time now, using the (undocumented) MATCHES() function. I have now changed this to comply with the REGEXP operator. Functionality is PERL (PCRE)
Since I have not been answering queries for some time now, because I was too busy, I will try to address some of the accumulated issues in this announcement, as well: >2. I have a table with signed 32-bit integers. Doing queries with negative >values doesn't work. I have to specify the 2's complement value to get it >working. Sqlite3Explorer does not support 64-bit UNSIGNED integers (32-bit is ok). This is a Delphi limitation, and not likely to be solved. >>1. The rowid (implicit column) is not displayed. of course. you need to add it to the SELECT statement explicitly. If any other product is showing you this, they are monkeying with your SQL. >I Have two databases with identical schema but different data. Open one >.database, view data in one table. Open the other database, the data shown >in the table is for the original database. Edit the data, and Update >database. The second database is updated with the changed information if >the same record exists there; otherwise you get: --------------------------- sqlite3explorer --------------------------- resolver: unexpected count of affected records: 0. --------------------------- OK --------------------------- This is a feature, not a bug. it allows you to load data, open another database and apply changes there. This works as designed. if you do not need this, simply do not use it. >Further to these, I've found that viewing of text data in the grid is >limited to 255 characters. Is it possible to make the default a lot bigger >or have a way of "zooming" a field to get the final value. Not strictly true. If you work in untyped mode, or if you work in typed mode, but your columns do NOT contain size information, then, yes, the columns default to a size of 255. Version 1.6 changes this to 8192. Also, a workaround for the previous versions would be to define your columns properly , such as : name varchar (wrong) name varchar(1200) (correct)
