AW: AW: [Openinteract-dev] Paged Results with CommonHandler

[<Mar...@be...>]

For each search id are two files present in our $website_dir/overflow.
The files only named by the search id are looking like the following =
format:

oit::MyClass-->3675
oit::MyClass-->3831
oit::MyClass-->3860
oit::MyClass-->3863

The files with the meta information are looking like this example here:

$VAR1 =3D {
          'num_extra' =3D> 0,
          'filename' =3D> undef,
          'extra_name' =3D> undef,
          'search_id' =3D> 'UIRFZUSBYAWEHQJODKSQ',
          'has_extra' =3D> undef,
          'num_records' =3D> 4,
          'results_dir' =3D> '/oit/overflow',
          'time' =3D> 1011616101,
          'record_class' =3D> 'oit::MyClass
        };

Marcus
> -----Urspr=FCngliche Nachricht-----
> Von:	Chris Winters [SMTP:ch...@cw...]
> Gesendet am:	Montag, 21. Januar 2002 15:25
> An:	Mar...@be...
> Cc:	ope...@li...
> Betreff:	Re: AW: [Openinteract-dev] Paged Results with CommonHandler
>=20
> On Mon, 2002-01-21 at 09:15, Mar...@be... wrote:
> > we are using OpenInteract 1.36 and CommonHandler 1.34.=20
> >=20
> > With the MY_SEARCH_RESULTS_PAGED option, the iterator which is =
returned
> by
> > ResultsManage has no entries. The get_next() call returns nothing.
> Calling
> > the has_next() method returns false, too.=20
> >=20
> > Without the MY_SEARCH_RESULTS_PAGED option the iterator returned by =
the
> > CommonHandler's _search_build_and_run method contains the proper
> results.
> > With get_next I can walk through my results.
> >=20
> > In both cases the query to search for was the same, the only =
difference
> was
> > given by MY_SEARCH_RESULTS_PAGED.=20
> >=20
> > The search results were properly saved by ResultsManage, so it =
seems
> > something goes wrong on retrieving the search results. Do you have =
an
> idea?
>=20
> This is very strange. When you say the search results were saved
> properly, do you mean that OI created the serialized search =
information
> files in the $WEBSITE_DIR/overflow directory? Can you check that
> directory and see if the files have any content?
>=20
> Chris
>=20
> --=20
> Chris Winters (ch...@cw...)
> Building enterprise-capable snack solutions since 1988.