Hi,
There is no difference. In addition to the index for paging, you just have
a tag property. So
# or SearchableModel
class MyProperty(db.Model):
# For paging
index = db.IntegerProperty()
my_tags = db.StringListProperty()
For the first page, you do a fetch like this:
results = MyPropert
I've watched the video...my question is how to make paging index for tag and
term for search?
On Wed, Dec 10, 2008 at 1:25 AM, Marzia Niccolai <[EMAIL PROTECTED]> wrote:
> Hi,
>
> By index I mean whatever index you are using for pagination, an integer
> property as described in the building scala
Hi,
By index I mean whatever index you are using for pagination, an integer
property as described in the building scalable web applications talk:
http://sites.google.com/site/io/building-scalable-web-applications-with-google-app-engine
This should work to page searchable entities as well. Simply
I haven't got it...what is the 'index' for in your code? For different tags,
they have different index for an object.
3rd question is about search the model.
On Tue, Dec 9, 2008 at 4:03 AM, Marzia Niccolai <[EMAIL PROTECTED]> wrote:
> Hi,
>
> If you store the tags in a list, you should be able fi
Hi,
If you store the tags in a list, you should be able filter on that list
using a simple equals filter, something like:
MyProperty.all().filter('my tags =', tag).filter('index <=',
starting_index).fetch(10)
Assuming you don't have a large number of tags (a couple per entry), this
shouldn't res
