blogs

We have just implemented a scaffold of Google Map!

If you have a table with latitude and longitude, you are just minutes away from a working search with Google Map.

Well, it's only in beta, because there are some problems with IE. If you find out what's wrong, please let us know!

Scaffold can do lots more. Just let us know what you want. Or simply send us your templates, and we can convert it into re-usable scaffold.

We recently added several partial scaffolding, which you can choose to apply to the templates that're generated from scaffolding.

One of the most interesting one should be the fancy Suggest-As-You-Type. Users can start typing and some words or phrases matching what's already typed will show up as hints.

BTW: To see this feature in action, you need to configure which database column to spell check first.

Other partial scaffoldings, for example, multi-selection narrowBy, tag cloud, pagination, are relatively new. You may also want to check them out.

The scaffolding directory structure is also changed, so that you can add your own scaffolding without being overwritten when DBSight upgrades.

The strong feature of DBSight is searching databases, but because DBSight is only for database, it has been the shortcoming also.

But thing's changed! Now DBSight can search outside database also!

Basically you just need to implement a simple abstract java class, where you can retrieve content from any data source, like files on disk, XML feeds via HTTP, etc.

The API is simple, yet able to handle incremental indexing and a re-creating index. You just need to select the content and submit it to DBSight. The content is processed in a streaming fashion, without consuming too much memory. DBSight will handle uniqueness checking and content updating in the background.

Spell Checking has been in DBSight from the very beginning. However, it was based on a word file, instead of words taken from the indexes.

Now with DBSight 2.0.5 beta, with just one click from the dashboard, the dictionary can be generated for each index. So now you would have more reasonable spell check recommendations.

And you can specify which field needs spell checking. I think you don't want to spell check on numbers, or URLs, or dates. Just configure them via the new "Spell Check" menu.

Let us know if you have some suggestions or other interesting ideas.

This thread will talk about some interesting new features. First of all, Batching Subsequent Queries.

We are working on DBSight 2.0, which should improve dbsight on many fronts. One of the improvement is the option to Batching Subsequent Queries.

Previously, you have a subsequent query like:

 select * from comments where article_id = ?

It'll fetch all comments of an article. But this query will run for each article. DBSight needs to send the same query to the database.

Now, you can write the query like:

 select * from comments where article_id in ( ? )

DBSight will recognize this pattern, and expand the query to:

Well, I have to say I am jealous. 2.6 million Euro is a lot of money. But congratulation!

DBSight's flexible and highly scalable and memory efficient search is one of the customer's secret weapons!

DBSight gives user flexibility to create and adjust search easily, without thinking much about search details.

The customer used DBSight multi-facet search extensively. A recent algorithm change reduced the customer's memory usage by half!

Anonymous customer, keep it going!

DBSight users, you can do it too!

Mike has a great usage of Lucene http://blogs.atlassian.com/rebelutionary/archives/2007/04/my_serverside_java_symposium_2007_presen.html

First of all, fantastic effort!

But I see from the presentation that he is having problems for large Lucene indexes, and he wants to resolve it using Eden space strategy, and a pretty complicated strategy for clustered Lucene index .

DBSight is using Eden space strategy already, and uses a simple and robust Lucene index replication mechanism for clustering. It requires a dedicated Indexing server, but it easily relieves all other nodes' heavy Indexing process.

In the latest beta, we have added scripting capability, and you can easily customize it to whatever you want!

For example, if you want to make a copy of the index, or ftp it to another machine, or send an email to anyone.

Sky is the limit! More details will be posted on the wiki.

The Velocity verbose log errors are very annoying. I was tired of it also, but just let it be. Several people are complaining about it recently. So I took 10 minutes to look though the web, and found the trick.

Super simple, just edit velocity.properties file, add one line there

 runtime.log.logsystem.class=org.apache.velocity.runtime.log.Log4JLogSystem

Right. That's it. Finally Velocity is quiet now.