I do use joins. I know I have a left join in there somewhere :) So no,
I don't have support for GAE out of box.
I actually designed blogitizor to be more CMS oriented, hence I use
the name Pages instead of Posts. However my first and foremost goal
was to deprecate my wordpress blog, now that that is completed I am
taking a step back.
It is an interesting development theory on GAE vs Relational database,
relational databases you need to normalize the tables, so you need
joins, however on GAE you need just a bigtable, so no joins and lots
of repeated data.
So the whole design of your data changes, comletely whether you are on
GAE/or using a notable database like mongo or couch, or using a
relational database like mysql postgres or sqlite.
So here the real question comes in for supporting GAE vs relational,
we actually need a layout on top of the DAL that can translate for us
queries based on what platform we are on.
So I am thinking that all queries will have to be meta classes, so
instead of doing db(db.page.id > 0).select(limitby=(1,15)) you will do
Posts.get(limitby, etc etc)
class Query
def get
def update
def insert
def delete
class PostQueryBigTableAdapter(Query)
def get(category="web2py")
return db(db.post.categories == "web2py").select()
class PostQueryRelationalAdapter(Query)
def get(category="web2py")
return db(db.post.category == db.category.id & db.category.name
== category).select()
This would allow for seamless integration into either a relational
database or GAE and be able to monopolize on the features of both. You
sacrifice alot of speed doing relation like tables on Google Big
Table, and you lose a almost making your application not run by doing
BIgTable things on a relational database.
-Thadeus
On Mon, Jan 25, 2010 at 5:29 PM, Richard <[email protected]> wrote:
> that would be great if you further developed blogitizor so it had the
> functionality of a CMS.
> If there anything preventing blogitizor running on GAE?
>
>
> On Jan 26, 1:55 am, Thadeus Burgess <[email protected]> wrote:
>> And because of this I have been looking and designing in my head how
>> to make blogitizor not just a blog engine, but a pluggable system.
>>
>> -Thadeus
>>
>>
>>
>> On Mon, Jan 25, 2010 at 8:54 AM, Thadeus Burgess <[email protected]>
>> wrote:
>> > Well I have been looking at a bunch of them, because a CMS can be a
>> > blog and a blog is a stripped down CMS.
>>
>> > Ive noticed that most CMS systems are actually just pluggable
>> > frameworks, in which you install the features you want.
>>
>> > Take redmine for example, its a bug tracking software like trac, but
>> > implemented in such a way you can install a blog, your own themes,
>> > hell I could make it look and act exactly like my current website with
>> > the right plugin except for the fact I don't know ruby.
>>
>> > HazelCMS is done in a plugin fashion as well, you just install a
>> > component and it appears, im sure you could write a version control
>> > and have it hook into hazelcms as well.
>>
>> > So really Ive wondered do we need a CMS or a blog or a wiki, or do we
>> > need a true pluggable system that can become anything with the right
>> > mix and match of plugins
>>
>> > -Thadeus
>>
>> > On Mon, Jan 25, 2010 at 12:05 AM, Richard <[email protected]> wrote:
>> >> ah I was also attracted to the admin look and feel.
>>
>> >> web2py needs a RadiantC
>
> --
> You received this message because you are subscribed to the Google Groups
> "web2py-users" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/web2py?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en.
