hello, i'd like to know whether it is best to use classes or relational databases for a (medium ?) sized project involving about 1000 new documents a month (average interconnection between them) and about 2 years of backlogs (each doc being about 1500 signs). i would love to do it entirely in zope (classes + methods + dtml) but i'm not sure wheter this is a good idea or if i can make everything i'm used to like in a relational database. to make it more clear, i'll make an example. let's say i am dealing with news-like sutff i have the following tree : news news/sport news/sport/20010406_0236 news/sport/20010406_0345 news/sport/XXXXXXXXXXXXX (being yyyymmdd_hhmm) news/art news/art/20010406_0236 news/art/20010406_0345 news/art/XXXXXXXXXXXXX (being yyyymmdd_hhmm too) i'm using classe for these yyyymmdd_hhmm objects and i'd like to sort them according to date or author both in separate folders (newest items in sports) or to pick them from both (5 most recent items from both folders for example). how do i do that in dtml ? (i'd prefer doing it in dtml than in python because people who will be in charge afterwards will have less trouble managing it). <dtml-in xxx sort="date"> would do the trick inside a folder, but how do i do it in both folders ???? furthermore, is it a good idea to keep this in the zodb or is it best to put it in another outside database (mysql most probably) ? thx, $ven
I'd suggest our new DBObjects. They implement REAL classes, that are stored in a relational database - PostgreSQL, as MySQL is not too well-suited for transactions etc. But DBObjects are not for starters yet. Be prepared for reading the code and stuff like that. Currently, DBObjects just stores a very small footprint in the ZODB to make sure the objects can use all the Zope security etc. The data is stored in the SQL DB, so you can just use SQL for queries. The basic queries are auto-generated, like INSERTs or DELETEs, ... Joachim.
i'd like to know whether it is best to use classes or relational databases for a (medium ?) sized project involving about 1000 new documents a month (average interconnection between them) and about 2 years of backlogs (each doc being about 1500 signs).
i would love to do it entirely in zope (classes + methods + dtml) but i'm not sure wheter this is a good idea or if i can make everything i'm used to like in a relational database.
to make it more clear, i'll make an example. let's say i am dealing with news-like sutff i have the following tree :
news news/sport news/sport/20010406_0236 news/sport/20010406_0345 news/sport/XXXXXXXXXXXXX (being yyyymmdd_hhmm) news/art news/art/20010406_0236 news/art/20010406_0345 news/art/XXXXXXXXXXXXX (being yyyymmdd_hhmm too)
i'm using classe for these yyyymmdd_hhmm objects and i'd like to sort them according to date or author both in separate folders (newest items in sports) or to pick them from both (5 most recent items from both folders for example).
how do i do that in dtml ? (i'd prefer doing it in dtml than in python because people who will be in charge afterwards will have less trouble managing it).
<dtml-in xxx sort="date"> would do the trick inside a folder, but how do i do it in both folders ????
furthermore, is it a good idea to keep this in the zodb or is it best to put it in another outside database (mysql most probably) ?
thx,
$ven
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
I'd suggest our new DBObjects. They implement REAL classes, that are stored in a relational database - PostgreSQL, as MySQL is not too well-suited for transactions etc. But DBObjects are not for starters yet. Be prepared for reading the code and stuff like that.
lol, i'm still using zope ;-)))))
Currently, DBObjects just stores a very small footprint in the ZODB to make sure the objects can use all the Zope security etc. The data is stored in the SQL DB, so you can just use SQL for queries. The basic queries are auto-generated, like INSERTs or DELETEs, ...
sounds pretty nice in fact, i'll look into it... is it alpha software, beta, or can i rely on it for such a project (about 20.000 docs of 1500 signs approx) ? what are the shortcommings of using *normal* classes (appart from the fact that data.fs is gonna get real big ? a] does it slow down to a crawl ? b] does it crash, smoke and burn ? c] it is hjust baaaad practive ? d] ? $ven
is it alpha software, beta, or can i rely on it for such a project (about 20.000 docs of 1500 signs approx) ?
It is stable, but as it is not packed up nicely yet, let's call it a beta.
what are the shortcommings of using *normal* classes (appart from the fact that data.fs is gonna get real big ?
a] does it slow down to a crawl ? b] does it crash, smoke and burn ? c] it is hjust baaaad practive ? d] ?
I guess Zope could handle a lot of data in the ZODB without "crashing, smoking and burning". As far as I know, there just is some limit where the lookup-tables of the ZODB implementation get VERY big. And of course on some older Linuxes you will face the 2 GB-limit (or use multiple mounted storages, which is a bit more complicated than plain out-of-the-box Zope). For what you are planning to do, the limit will be the ZCatalog. You will need it for searching stuff in more than one folder. ZCatalog is getting better, but I still would not completely trust it for very large amounts of data. Joachim.
I'd suggest our new DBObjects. They implement REAL classes, that are stored in a relational database - PostgreSQL, as MySQL is not too well-suited for transactions etc. But DBObjects are not for starters yet. Be prepared for reading the code and stuff like that. Currently, DBObjects just stores a very small footprint in the ZODB to make sure the objects can use all the Zope security etc. The data is stored in the SQL DB, so you can just use SQL for queries. The basic queries are auto-generated, like INSERTs or DELETEs, ... Joachim.
i'd like to know whether it is best to use classes or relational databases for a (medium ?) sized project involving about 1000 new documents a month (average interconnection between them) and about 2 years of backlogs (each doc being about 1500 signs).
i would love to do it entirely in zope (classes + methods + dtml) but i'm not sure wheter this is a good idea or if i can make everything i'm used to like in a relational database.
to make it more clear, i'll make an example. let's say i am dealing with news-like sutff i have the following tree :
news news/sport news/sport/20010406_0236 news/sport/20010406_0345 news/sport/XXXXXXXXXXXXX (being yyyymmdd_hhmm) news/art news/art/20010406_0236 news/art/20010406_0345 news/art/XXXXXXXXXXXXX (being yyyymmdd_hhmm too)
i'm using classe for these yyyymmdd_hhmm objects and i'd like to sort them according to date or author both in separate folders (newest items in sports) or to pick them from both (5 most recent items from both folders for example).
how do i do that in dtml ? (i'd prefer doing it in dtml than in python because people who will be in charge afterwards will have less trouble managing it).
<dtml-in xxx sort="date"> would do the trick inside a folder, but how do i do it in both folders ????
furthermore, is it a good idea to keep this in the zodb or is it best to put it in another outside database (mysql most probably) ?
thx,
$ven
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
At 02:45 AM 4/6/01 +0200, you wrote:
<snip mail>
I agree with Joachim. This is a perfect job for DBObject, providing you with the best of both worlds: On one hand you can still use your known SQL Queries and on the other hand you have classes. What else do you want? Check out the DBObjects project page at: http://demo.iuveno-net.de. It also comes with an API Documentation and the code is very well documented, so that you can see what happens. We also makde a small demo product that uses DBObjects, in order to demonstrate how to make a Python Product using DBObjects. If you have further questions or need help, feel free to contact me any time. Regards, Stephan -- Stephan Richter CBU - Physics and Chemistry Student Web2k - Web Design/Development & Technical Project Management
participants (3)
-
Error -
Joachim Werner -
Stephan Richter