date:20081202

Re: DataImportHandler: Deleteing from index and db; lastIndexed id feature

2008-12-02 Thread Noble Paul നോബിള്‍ नोब्ळ्

On Tue, Dec 2, 2008 at 3:01 PM, Marc Sturlese [EMAIL PROTECTED] wrote:

Hey there,

I have my dataimporthanlder almost completely configured. I am missing three
goals. I don't think I can reach them just via xml conf or transformer and
sqlEntitProcessor plugin. But need to be sure of that.
If there's no other way I will hack some solr source classes, would like to
know the best way to do that. Once I have it solved, I can upload or post
the source in the forum in case someone think it can be helpful.

1.- Every time I execute dataimporthandler (to index data from a db), at the
start time or end time I need to delete some expired documents. I have to
delete them from the database and from the index. I know wich documents must
be deleted because of a field in the db that says it. Would not like to
delete first all from DB or first all from index but one from index and one
from doc every time.

You can override the init() destroy() of the SqlEntityProcessor and
use it as the processor for the root entity. At this point you can run
the necessary db queries and solr delete queries . look at
Context#getSolrCore() and Context#getdataSource(String)

The delete mark is setted as an update in the db row so I think I could
use deltaImport. Don't know If deletedPkQuery is the way to do that. Can not
find so much information about how to make it work. As deltaQuery modifies
docs (delete old and insert new) I supose it must be a easy way to do this
just doing the delete and not the new insert.
deletedPkQuery does everything first. it runs the query and uses that
to identify the deleted rows.

2.-This is probably my most difficult goal.
Deltaimport reads a timestamp from the dataimport.properties and modify/add
all documents from db wich were inserted after that date. What I want is to
be able to save in the field the id of the last idexed doc. So in the next
time I ejecute the indexer make it start indexing from that last indexed id
doc.
You can use a Transformer to write something to the DB.
Context#getDataSource(String) for each row

The point of doing this is that if I do a full import from a db with lots of
rows the app could encounter a problem in the middle of the execution and
abort the process. As deltaquey works I would have to restart the execution
from the begining. Having this new functionality I could optimize the index
and start from the last indexed doc.
I think I should begin modifying the SolrWriter.java and DocBuilder.java.
Creating functions like getStartTime, persistStartTime... for ID control

3.-I commented before about this last point. I want to give boost to doc
fields at indexing time.
Adding fieldboost is a planned item.

It must work as follows .
Add a special value $fieldBoost.fieldname to the row map

And DocBuilder should respect that. You can raise a bug and we can
commit it soon.
How can I do to rise a bug?
https://issues.apache.org/jira/secure/CreateIssue!default.jspa

Thanks in advance

--
View this message in context:
http://www.nabble.com/DataImportHandler%3A-Deleteing-from-index-and-db--lastIndexed-id-feature-tp20788755p20788755.html
Sent from the Solr - User mailing list archive at Nabble.com.

--
--Noble Paul

Re: DataImportHandler: Deleteing from index and db; lastIndexed id feature

2008-12-02 Thread Marc Sturlese

Thanks I really apreciate your help.

I didn't explain myself so well in here:

2.-This is probably my most difficult goal.
Deltaimport reads a timestamp from the dataimport.properties and
modify/add
all documents from db wich were inserted after that date. What I want is
to
be able to save in the field the id of the last idexed doc. So in the next
time I ejecute the indexer make it start indexing from that last indexed
id
doc.
You can use a Transformer to write something to the DB.
Context#getDataSource(String) for each row

When I said:

be able to save in the field the id of the last idexed doc
I made a mistake, wanted to mean :

be able to save in the file (dataimport.properties) the id of the last
indexed doc.
The point would be to do my own deltaquery indexing from the last doc
indexed id instead of the timestamp.
So I think this would not work in that case (it's my mistake because of the
bad explanation):

You can use a Transformer to write something to the DB.
Context#getDataSource(String) for each row

It is because I was saying:
I think I should begin modifying the SolrWriter.java and DocBuilder.java.
Creating functions like getStartTime, persistStartTime... for ID control

I am in the correct direction?
Sorry for my englis and thanks in advance

Noble Paul നോബിള്‍ नोब्ळ् wrote:

On Tue, Dec 2, 2008 at 3:01 PM, Marc Sturlese [EMAIL PROTECTED]
wrote:

Hey there,

I have my dataimporthanlder almost completely configured. I am missing
three
goals. I don't think I can reach them just via xml conf or transformer
and
sqlEntitProcessor plugin. But need to be sure of that.
If there's no other way I will hack some solr source classes, would like
to
know the best way to do that. Once I have it solved, I can upload or post
the source in the forum in case someone think it can be helpful.

1.- Every time I execute dataimporthandler (to index data from a db), at
the
start time or end time I need to delete some expired documents. I have to
delete them from the database and from the index. I know wich documents
must
be deleted because of a field in the db that says it. Would not like to
delete first all from DB or first all from index but one from index and
one
from doc every time.

The delete mark is setted as an update in the db row so I think I could
use deltaImport. Don't know If deletedPkQuery is the way to do that. Can
not
find so much information about how to make it work. As deltaQuery
modifies
docs (delete old and insert new) I supose it must be a easy way to do
this
just doing the delete and not the new insert.
deletedPkQuery does everything first. it runs the query and uses that
to identify the deleted rows.

2.-This is probably my most difficult goal.
Deltaimport reads a timestamp from the dataimport.properties and
modify/add
all documents from db wich were inserted after that date. What I want is
to
be able to save in the field the id of the last idexed doc. So in the
next
time I ejecute the indexer make it start indexing from that last indexed
id
doc.
You can use a Transformer to write something to the DB.
Context#getDataSource(String) for each row

The point of doing this is that if I do a full import from a db with lots
of
rows the app could encounter a problem in the middle of the execution and
abort the process. As deltaquey works I would have to restart the
execution
from the begining. Having this new functionality I could optimize the
index
and start from the last indexed doc.
I think I should begin modifying the SolrWriter.java and DocBuilder.java.
Creating functions like getStartTime, persistStartTime... for ID control

3.-I commented before about this last point. I want to give boost to doc
fields at indexing time.
Adding fieldboost is a planned item.

It must work as follows .
Add a special value $fieldBoost.fieldname to the row map

And DocBuilder should respect that. You can raise a bug and we can
commit it soon.
How can I do to rise a bug?
https://issues.apache.org/jira/secure/CreateIssue!default.jspa

Thanks in advance

--
--Noble Paul

--
View this message in context:
http://www.nabble.com/DataImportHandler%3A-Deleteing-from-index-and-db--lastIndexed-id-feature-tp20788755p20790542.html
Sent from the Solr - User mailing list archive at Nabble.com.

Re: PHPResponseWriter problem with (de)serialization (spellchecker)

2008-12-02 Thread Yonik Seeley

On Tue, Dec 2, 2008 at 6:39 AM, Steffen B. [EMAIL PROTECTED] wrote:
 Little update: this behaviour can be easily reproduced with the example
 configuration that comes with Solr:
 After uncommenting line 733 in
 apache-solr-nightly/example/solr/conf/solrconfig.xml (which activates the
 PHPS queryResponseWriter) loading this URL on the example index shows the
 same problem:
 http://localhost:8983/solr/spellCheckCompRH?cmd=q=ipodspellcheck=truespellcheck.extendedResults=truespellcheck.onlyMorePopular=truewt=phps

 [...]s:10:spellcheck;a:1:{s:11:suggestions;a:1:{s:16:correctlySpelled;true}}}

 As I'm no Java crack and have neither time nor knowledge to debug the class
 myself, I can only offer to (re)open a task in Jira. Any opinions on this?

Hi Steffen, was there previosly JIRA issue already open specifically
for this issue?  If not, please do open a new issue.

-Yonik

Re: PHPResponseWriter problem with (de)serialization (spellchecker)

2008-12-02 Thread Steffen B.


No, this issue is new. But there was a general PHPResponseWriter task...
I opened a new one: https://issues.apache.org/jira/browse/SOLR-892
Feel free to move / edit / merge it. ;) I hope I made the problem clear.
~ Steffen


Yonik Seeley wrote:
 
 On Tue, Dec 2, 2008 at 6:39 AM, Steffen B. [EMAIL PROTECTED]
 wrote:
 Little update: this behaviour can be easily reproduced with the example
 configuration that comes with Solr:
 After uncommenting line 733 in
 apache-solr-nightly/example/solr/conf/solrconfig.xml (which activates the
 PHPS queryResponseWriter) loading this URL on the example index shows the
 same problem:
 http://localhost:8983/solr/spellCheckCompRH?cmd=q=ipodspellcheck=truespellcheck.extendedResults=truespellcheck.onlyMorePopular=truewt=phps

 [...]s:10:spellcheck;a:1:{s:11:suggestions;a:1:{s:16:correctlySpelled;true}}}

 As I'm no Java crack and have neither time nor knowledge to debug the
 class
 myself, I can only offer to (re)open a task in Jira. Any opinions on
 this?
 
 Hi Steffen, was there previosly JIRA issue already open specifically
 for this issue?  If not, please do open a new issue.
 
 -Yonik
 
 

-- 
View this message in context: 
http://www.nabble.com/PHPResponseWriter-problem-with-%28de%29serialization-%28spellchecker%29-tp20703677p20792680.html
Sent from the Solr - User mailing list archive at Nabble.com.

Re: PHPResponseWriter problem with (de)serialization (spellchecker)

2008-12-02 Thread Steffen B.


Little update: this behaviour can be easily reproduced with the example
configuration that comes with Solr:
After uncommenting line 733 in
apache-solr-nightly/example/solr/conf/solrconfig.xml (which activates the
PHPS queryResponseWriter) loading this URL on the example index shows the
same problem:
http://localhost:8983/solr/spellCheckCompRH?cmd=q=ipodspellcheck=truespellcheck.extendedResults=truespellcheck.onlyMorePopular=truewt=phps

[...]s:10:spellcheck;a:1:{s:11:suggestions;a:1:{s:16:correctlySpelled;true}}}

As I'm no Java crack and have neither time nor knowledge to debug the class
myself, I can only offer to (re)open a task in Jira. Any opinions on this?

~ Steffen


Steffen B. wrote:
 
 Hi everyone,
 maybe it's just me, but whenever I try to deserialize a Solr response that
 contains the spellchecker with spellcheck.extendedResults, it fails. I'm
 using PHP5 and everthing is pretty much up-to-date.
 lst name=spellcheck
   lst name=suggestions
 bool name=correctlySpelledtrue/bool
   /lst
 /lst
 will be converted to
 [...] 
 s:10:spellcheck;a:1:{s:11:suggestions;a:1:{s:16:correctlySpelled;true}}}
 which is not deserializeable with unserialize():
 Notice: unserialize() [function.unserialize]: Error at offset 305 of 312
 bytes in /Solr/Client.php on line 131
 
 PHP, on the other hand, serializes an array this way:
 echo
 serialize(array(spellcheck=array(suggestions=array(correctlySpelled=true;
 to
 a:1:{s:10:spellcheck;a:1:{s:11:suggestions;a:1:{s:16:correctlySpelled;b:1;}}}
 
 So there are obviously differences in the way boolean vars are converted,
 though I'm not sure if it's a problem with the PHPResponseWriter or with
 my setup. Can anyone confirm this behaviour?
 
 

-- 
View this message in context: 
http://www.nabble.com/PHPResponseWriter-problem-with-%28de%29serialization-%28spellchecker%29-tp20703677p20790504.html
Sent from the Solr - User mailing list archive at Nabble.com.

Re: Dealing with field values as key/value pairs

2008-12-02 Thread Stephane Bailliez



Yeh, sorry was not clear in my question. Storage would end up being done 
the same way of course


I guess I'm more looking for feedback about what people have used as a 
strategy to handle this type of situation. This goes for faceting as well.


Assuming I do faceting by author and there is 2 authors with the same 
name. Does not work right.


So discovering hot water, here, the facet value is best expressed with 
identifiers which would uniquely identify your author. Then you lose the 
'name' and you need to effectively get it.


But if you want to effectively also offer the ability to offer the name 
of the author in your solr response in a 'standalone' way (ie: don't 
rely an another source of data, like the db where is stored that 
mapping) ...then you need to store this data in a convenient form in the 
index to be able to access it later.


So i'm basically looking for design pattern/best practice for that 
scenario based on people's experience.



I was also thinking about storing each values into dynamic fields such 
as 'metadata_field_identifier' and then assuming I have a facet 
'facet_field' which stores identifiers,  use a search component to 
provide the mapping as an 'extra' in the response  and give the mapping 
in another section of the response (similar to the debug, facets, etc)


ie: something like:
mapping: {

  'field1': { 'identifier1': 'value1', 'identifier2': 'value2' },

  'field2': { 'identifierx': 'valuex', 'identifiery': 'valuey' }
}

does that make sense ?

-- stephane

Noble Paul നോബിള്‍ नोब्ळ् wrote:

In the end lucene stores stuff as strings.

Even if you do store your data as map FieldType , Solr May not be able
to treat it like a map.
So it is fine to put is the map as one single string

On Mon, Dec 1, 2008 at 10:07 PM, Stephane Bailliez [EMAIL PROTECTED] wrote:

Hi all,


I'm looking for ideas about how to best deal with a situation where I need
to deal with storing key/values pairs in the index for consumption in the
client.


Typical example would be to have a document with multiple genres where for
simplicity reasons i'd like to send both the 'id' and the 'human readable
label' (might not be the best example since one would immediatly say 'what
about localization', but in that case assume it's an entity such as company
name or a person name).

So say I have

field1 = { 'key1':'this is value1', 'key2':'this is value2' }


I was thinking the easiest (not the prettiest) solution would be to store it
as effectively a string 'key:this is the value' and then have the client
deal with this 'format' and then parse it based on 'key:value' pattern

Another alternative I was thinking may have been to use a custom field that
effectively would make the field value as a map key/value for the writer but
I'm not so sure it can really be done, haven't investigated that one deeply.

Any feedback would be welcome, solution might even be simpler and cleaner
than what I'm mentioning above, but my brain is mushy in the last couple of
weeks.

-- stephane

Re: Problem indexing on Oracle DB

2008-12-02 Thread Noble Paul നോബിള്‍ नोब्ळ्

cool

The only problem is that java.sql.Clob#getCharacterStream() is package
private and you have to use the oracle.sql.CLOB



On Tue, Dec 2, 2008 at 1:38 PM, Joel Karlsson [EMAIL PROTECTED] wrote:
 Thanks for your reply!

 I wrote such a transformer and now it seems to work perfectly. Here's the
 code for the transformer if anyone encounters the same problem, or if anyone
 want to improve it:

 import org.apache.solr.handler.dataimport.*;
 import oracle.sql.CLOB;
 import java.util.*;
 import java.io.*;

 public class ClobTransformer extends Transformer
 {
public MapString, Object transformRow(MapString, Object row, Context
 context)
{
ListMapString, String fields = context.getAllEntityFields();
for (MapString, String field : fields)
{
String toString = field.get(toString);
if (true.equals(toString))
{
String columnName = field.get(column);
CLOB clob = (CLOB)row.get(columnName);
if (clob != null)
{
StringBuffer strOut = new StringBuffer();
String app;
try {
BufferedReader br = new
 BufferedReader(clob.getCharacterStream());
while ((app=br.readLine())!=null)
strOut.append(app);
} catch (Exception e) { e.printStackTrace(); }

row.put(columnName, strOut.toString());
}
}
}
return row;

}
 }

 // Joel

 2008/12/2 Noble Paul നോബിള്‍ नोब्ळ् [EMAIL PROTECTED]

 Hi Joel,
 DIH does not translate Clob automatically to text.

 We can open that as an issue.
 meanwhile you can write a transformer of your own to read Clob and
 convert to text.

 http://wiki.apache.org/solr/DataImportHandler#head-4756038c418ab3fa389efc822277a7a789d27688


 On Tue, Dec 2, 2008 at 2:57 AM, Joel Karlsson [EMAIL PROTECTED]
 wrote:
  Thanks for your reply!
 
  I'm already using the DataImportHandler for indexing. Do I still have to
  convert the Clob myself or are there any built-in functions that I've
  missed?
 
  // Joel
 
 
  2008/12/1 Yonik Seeley [EMAIL PROTECTED]
 
  If you are querying Oracle yourself and using something like SolrJ,
  then you must convert the Clob yourself into a String representation.
 
  Also, did you look at Solr's DataImportHandler?
 
  -Yonik
 
  On Mon, Dec 1, 2008 at 3:11 PM, Joel Karlsson [EMAIL PROTECTED]
  wrote:
   Hello everyone,
  
   I'm trying to index on an Oracle DB, but can't seem to find any built
 in
   support for objects of type oracle.sql.Clob. The field I try to put
 the
  data
   into is of type text, but after indexing it only contains the
  Clob-objects
   string representation, i.e. something like [EMAIL PROTECTED]
  who
   knows how to get Solr to index the content of these objects rather
 than
  its
   string representation??
  
   Thanks in advance! // Joel
  
 
 



 --
 --Noble Paul





-- 
--Noble Paul

Re: Problem indexing on Oracle DB

2008-12-02 Thread Noble Paul നോബിള്‍ नोब्ळ्

no probs We can fix that using reflection. I shall give a patch w/ that.
Probably it is better to fix it in a Transformer



On Tue, Dec 2, 2008 at 1:56 PM, Joel Karlsson [EMAIL PROTECTED] wrote:
 True, but perhaps it works with java.sql.Clob as well, haven't tried it
 though.

 2008/12/2 Noble Paul നോബിള്‍ नोब्ळ् [EMAIL PROTECTED]

 cool

 The only problem is that java.sql.Clob#getCharacterStream() is package
 private and you have to use the oracle.sql.CLOB



 On Tue, Dec 2, 2008 at 1:38 PM, Joel Karlsson [EMAIL PROTECTED]
 wrote:
  Thanks for your reply!
 
  I wrote such a transformer and now it seems to work perfectly. Here's the
  code for the transformer if anyone encounters the same problem, or if
 anyone
  want to improve it:
 
  import org.apache.solr.handler.dataimport.*;
  import oracle.sql.CLOB;
  import java.util.*;
  import java.io.*;
 
  public class ClobTransformer extends Transformer
  {
 public MapString, Object transformRow(MapString, Object row,
 Context
  context)
 {
 ListMapString, String fields = context.getAllEntityFields();
 for (MapString, String field : fields)
 {
 String toString = field.get(toString);
 if (true.equals(toString))
 {
 String columnName = field.get(column);
 CLOB clob = (CLOB)row.get(columnName);
 if (clob != null)
 {
 StringBuffer strOut = new StringBuffer();
 String app;
 try {
 BufferedReader br = new
  BufferedReader(clob.getCharacterStream());
 while ((app=br.readLine())!=null)
 strOut.append(app);
 } catch (Exception e) { e.printStackTrace(); }
 
 row.put(columnName, strOut.toString());
 }
 }
 }
 return row;
 
 }
  }
 
  // Joel
 
  2008/12/2 Noble Paul നോബിള്‍ नोब्ळ् [EMAIL PROTECTED]
 
  Hi Joel,
  DIH does not translate Clob automatically to text.
 
  We can open that as an issue.
  meanwhile you can write a transformer of your own to read Clob and
  convert to text.
 
 
 http://wiki.apache.org/solr/DataImportHandler#head-4756038c418ab3fa389efc822277a7a789d27688
 
 
  On Tue, Dec 2, 2008 at 2:57 AM, Joel Karlsson [EMAIL PROTECTED]
  wrote:
   Thanks for your reply!
  
   I'm already using the DataImportHandler for indexing. Do I still have
 to
   convert the Clob myself or are there any built-in functions that I've
   missed?
  
   // Joel
  
  
   2008/12/1 Yonik Seeley [EMAIL PROTECTED]
  
   If you are querying Oracle yourself and using something like SolrJ,
   then you must convert the Clob yourself into a String representation.
  
   Also, did you look at Solr's DataImportHandler?
  
   -Yonik
  
   On Mon, Dec 1, 2008 at 3:11 PM, Joel Karlsson [EMAIL PROTECTED]
 
   wrote:
Hello everyone,
   
I'm trying to index on an Oracle DB, but can't seem to find any
 built
  in
support for objects of type oracle.sql.Clob. The field I try to put
  the
   data
into is of type text, but after indexing it only contains the
   Clob-objects
string representation, i.e. something like
 [EMAIL PROTECTED]
   who
knows how to get Solr to index the content of these objects rather
  than
   its
string representation??
   
Thanks in advance! // Joel
   
  
  
 
 
 
  --
  --Noble Paul
 
 



 --
 --Noble Paul





-- 
--Noble Paul

Re: Problem indexing on Oracle DB

2008-12-02 Thread Joel Karlsson

True, but perhaps it works with java.sql.Clob as well, haven't tried it
though.

2008/12/2 Noble Paul നോബിള്‍ नोब्ळ् [EMAIL PROTECTED]

 cool

 The only problem is that java.sql.Clob#getCharacterStream() is package
 private and you have to use the oracle.sql.CLOB



 On Tue, Dec 2, 2008 at 1:38 PM, Joel Karlsson [EMAIL PROTECTED]
 wrote:
  Thanks for your reply!
 
  I wrote such a transformer and now it seems to work perfectly. Here's the
  code for the transformer if anyone encounters the same problem, or if
 anyone
  want to improve it:
 
  import org.apache.solr.handler.dataimport.*;
  import oracle.sql.CLOB;
  import java.util.*;
  import java.io.*;
 
  public class ClobTransformer extends Transformer
  {
 public MapString, Object transformRow(MapString, Object row,
 Context
  context)
 {
 ListMapString, String fields = context.getAllEntityFields();
 for (MapString, String field : fields)
 {
 String toString = field.get(toString);
 if (true.equals(toString))
 {
 String columnName = field.get(column);
 CLOB clob = (CLOB)row.get(columnName);
 if (clob != null)
 {
 StringBuffer strOut = new StringBuffer();
 String app;
 try {
 BufferedReader br = new
  BufferedReader(clob.getCharacterStream());
 while ((app=br.readLine())!=null)
 strOut.append(app);
 } catch (Exception e) { e.printStackTrace(); }
 
 row.put(columnName, strOut.toString());
 }
 }
 }
 return row;
 
 }
  }
 
  // Joel
 
  2008/12/2 Noble Paul നോബിള്‍ नोब्ळ् [EMAIL PROTECTED]
 
  Hi Joel,
  DIH does not translate Clob automatically to text.
 
  We can open that as an issue.
  meanwhile you can write a transformer of your own to read Clob and
  convert to text.
 
 
 http://wiki.apache.org/solr/DataImportHandler#head-4756038c418ab3fa389efc822277a7a789d27688
 
 
  On Tue, Dec 2, 2008 at 2:57 AM, Joel Karlsson [EMAIL PROTECTED]
  wrote:
   Thanks for your reply!
  
   I'm already using the DataImportHandler for indexing. Do I still have
 to
   convert the Clob myself or are there any built-in functions that I've
   missed?
  
   // Joel
  
  
   2008/12/1 Yonik Seeley [EMAIL PROTECTED]
  
   If you are querying Oracle yourself and using something like SolrJ,
   then you must convert the Clob yourself into a String representation.
  
   Also, did you look at Solr's DataImportHandler?
  
   -Yonik
  
   On Mon, Dec 1, 2008 at 3:11 PM, Joel Karlsson [EMAIL PROTECTED]
 
   wrote:
Hello everyone,
   
I'm trying to index on an Oracle DB, but can't seem to find any
 built
  in
support for objects of type oracle.sql.Clob. The field I try to put
  the
   data
into is of type text, but after indexing it only contains the
   Clob-objects
string representation, i.e. something like
 [EMAIL PROTECTED]
   who
knows how to get Solr to index the content of these objects rather
  than
   its
string representation??
   
Thanks in advance! // Joel
   
  
  
 
 
 
  --
  --Noble Paul
 
 



 --
 --Noble Paul

Multi Language Search

2008-12-02 Thread tushar kapoor


Hi,

Before I start with Solr specific question, there is one thing I need to get
information on.

If I am a Russian user on a Russian Website  I want to search for indexes
having two Russian words how is the query term going to look like.

1. Russian Word 1 AND Russian Word 2

or rather,

2 . Russian Word 1 AND in Russian Russian Word 2

Now over to solr specific question. In case the answer to above is either 1.
or 2. how does one do it using Solr. I tried using the Language anallyzers
but I m not too sure how exactly it works.

Regards,
Tushar.
-- 
View this message in context: 
http://www.nabble.com/Multi-Language-Search-tp20789025p20789025.html
Sent from the Solr - User mailing list archive at Nabble.com.

Re: DataImportHandler: Deleteing from index and db; lastIndexed id feature

2008-12-02 Thread Noble Paul നോബിള്‍ नोब्ळ्

You can write the details to a file using a Transformer itself.

It is wise to stick to the public API as far as possible. We will
maintain back compat and your code will be usable w/ newer versions.

On Tue, Dec 2, 2008 at 5:12 PM, Marc Sturlese [EMAIL PROTECTED] wrote: