TurboGear : Another Identified Python Web Framework.

For loast couple days, I watch a new python web framework come in out. It named TurboGear. This web framework based on CherryPy, combined with SQLObject ORM, Kid template engine, and Mochikit javascript library.

As you know before, theres already a new python web framework come in on a last couple months, I was Django. I had been dive in it, until now. So, What is the different between the TurboGear and Django ? The way they create the framework. Django had beed create from scracth. TurboGear is take available tools out there and combined it to work.

I dont know which one of this framework gonna be survive.
The most interesting part of TurboGear get my eyes is AJAX features.
I think I'm gonna take a look on it.

ActiveGrid

Today, Mr.Reza Pahlevi, point me to ActiveGrid Project. Its good to hear one of my friend had an eye on linux and python. Its a project which gonna bring linux further.

Here, you'll deploy all your application onto couple linux box worked as a grid computing. It will use Linux , Apache, MySQL, and P-Programming language capability. So, its mean you can bring all your linux box, set them up as a linux box and tranform them into grid computing readibly, then deploy your application in it.

Its good right ?, cause, it would be a good and cheap solution. Build an Grid Computing using an Intel based architecture with a no-cost Linux Operating System, and also Develop your application using LAMP.

I had to eye on it man. You too.

Multiple Column on Primary Key

Some People might known about this topic, specialy if you one of DBA or DB Architect.
Its common used on Client/Server Technology, or Datawarehouse.

The purpose of Multiple Column on Primary Key Definition is Referential Integrity.
We can adopt this integrity into many table through foreign key mechanism, and it is help alot.

But, when you decided to used a web based application, you might face unflexiblity if you try to use this method. Unflexible huh ? yes, because a web based application always mention every single record with one unique id, based on a single column primary key. Thats why its not flexible for web based developer view.

Lets assume, If we decided to use a single column primary key, we might have a de-normalize problem. The DB Design might "not good" enough. Next, when soft.developer try to create their own query, they might face an "unnecessary column" in join command, since the term of "single column" in this case is not a subtitute column rather than an added column.

On the other side, If we keep moving with a Multiple Column on Primary Key, it will put an extra effort on an application for web developer when they define the CRUD (Create, Replace, Update and Delete) page.

So, how to solve this problem ?

For now, I choose a Multiple Column on Primary Key Design. It still made me satisfy.

I cant wait with Zope3

Realy, I can not wait to play with Zope 3 within Plone environtment. The current Plone still use Zope 2.8 engine with Five technology in it. U know, I dont think it would be good for me to put my application on top of The current plone. Why ? because I want my application should run on top of Zope 3. Thats why I can not wait anymore. Any idea ?