Hi Jelle,
It is a little off-topic, but no. I actually use both. It depends a
little on the use-case we have. In cases where the tasks is more
oriented to mesh-based data I use the XDMF format. This is XML for the
descriptive part and HDF5 (PyTables) for the heavy data. For
monitoring a physical t
> I will try to write a testcase in the next few weeks and post it here.
I'm very curious. I know you've been working with pytables too; did you chance
from using pytables ( hdf5 ) to couchdb?
-jelle
___
Pythonocc-users mailing list
Pythonocc-users@g
> Everything that stores objects accessible from a pythonic API could be, a
> priori, a suitable solution.
That's why it would be fun to use an ORM such that the actual DB you'll use can
be abstracted.
Too bad ( but understandable ) that sqlalchemy doesn't handle NoSQL DB's.
-jelle
___
Hi Marco,
Follow up on Jelle's notes :
"
I see, however, a NoSQL db is not going to give you a rich API querying the
DB, right?
"
and
"
Conceptually I planted it between serialization and a relational DB.
Is that correct?
"
As far as I understood the Cassandra db (don't know if it's the same for
I may be off base with this, but to my way of thinking cad models look
a lot like classical compiled software.
A pythonocc project might have some arbitrarily complex code
(pythonocc code) that produces objects that can also be stored in a
dataicentric form(step)
So, I am kind of thinking that a
Why not. Everything that stores objects accessible from a pythonic API could
be, a priori, a suitable solution.
I remember working with ZODB a few years ago (while trying to implement a
simple PDM system in python). I had a good feeling with it.
Thomas
2011/1/5 Bill Bedford
> Would a Zope ser
Would a Zope server with ZODB work as a repository? ZODB stores
everything as python objects.
--
Bill Bedford
"Man is an animal suspended in webs of significance he himself has spun"
-- Clifford Geertz
__
--
> >> *From:* pythonocc-users-boun...@gna.org [mailto:
> >> pythonocc-users-boun...@gna.org] *On Behalf Of *Thomas Paviot
> >> *Sent:* Thursday, December 30, 2010 7:43 AM
> >> *To:* pythonOCC users mailing list.
> >> *Subject:* R
2011/1/5 Thomas Paviot
> 2011/1/5 jelle feringa
>
> Guys, I'm not much of a DB expert, but a NoSQL db like cassandra is really
>> built specifically for web 2.0 realtime applications with trillions of
>> users. Query's are ran by code rather than sql statement and the DB is
>> reduced to storing
2011/1/5 jelle feringa
> Guys, I'm not much of a DB expert, but a NoSQL db like cassandra is really
> built specifically for web 2.0 realtime applications with trillions of
> users. Query's are ran by code rather than sql statement and the DB is
> reduced to storing / retrieving key/values ( on a
Hi Jelle,
> I *love* being corrected ;)
I love to correct :).
> I see, however, a NoSQL db is not going to give you a rich API querying the
> DB, right?
Well, it depends a little on what you mean. For NoSQL db's as far as I
know, there is
no standard like SQL. However, if you talk about CouchDB, yo
e replication wouldnt have problems getting
>> through
>> firewalls?
>>
>> --
>> *From:* pythonocc-users-boun...@gna.org [mailto:
>> pythonocc-users-boun...@gna.org] *On Behalf Of *Thomas Paviot
>> *Sent:* Thursday, December 30, 2010 7:43 AM
>> *To:* pythonOCC users
Dear All,
Interesting discussion, so here are my 2 cents.
First a disclaimer, I am no database expert at all, but have
experimented with sqlalchemy, sqlite etc. In addition, I recently
experimented with CouchDB which is a NoSQL database. I don't agree
with Jelle that NoSql db's are really built f
Guys, I'm not much of a DB expert, but a NoSQL db like cassandra is really
built specifically for web 2.0 realtime applications with trillions of
users. Query's are ran by code rather than sql statement and the DB is
reduced to storing / retrieving key/values ( on a large number of machines
).
I'm
through
> firewalls?
>
> --
> *From:* pythonocc-users-boun...@gna.org [mailto:
> pythonocc-users-boun...@gna.org] *On Behalf Of *Thomas Paviot
> *Sent:* Thursday, December 30, 2010 7:43 AM
> *To:* pythonOCC users mailing list.
> *Subject:* Re: [Pythonocc-users] writing OCC d
automatically finding and resolving all of the dependencies ( including
> transitive ones ) from repositories storing the dependencies
>
> ----------
> *From:* pythonocc-users-boun...@gna.org [mailto:
> pythonocc-users-boun...@gna.org] *On Behalf Of *Thomas Pavio
om repositories storing the dependencies
_
From: pythonocc-users-boun...@gna.org
[mailto:pythonocc-users-boun...@gna.org] On Behalf Of Thomas Paviot
Sent: Thursday, December 30, 2010 4:00 AM
To: jelleferi...@gmail.com; pythonOCC users mailing list.
Subject: Re: [Pythonocc-users] writing OC
[mailto:pythonocc-users-boun...@gna.org] On Behalf Of Thomas Paviot
Sent: Thursday, December 30, 2010 7:43 AM
To: pythonOCC users mailing list.
Subject: Re: [Pythonocc-users] writing OCC data to a db
One more information: there are 2 high level clients for Cassandra/Thrift :
Pycassa (http://github.com/pycassa
One more information: there are 2 high level clients for Cassandra/Thrift :
Pycassa (http://github.com/pycassa/pycassa) and Telephus (
http://github.com/driftx/Telephus).
2010/12/30 Thomas Paviot
> A few months ago, I had a look to the Apache Cassandra project (
> http://cassandra.apache.org/),
A few months ago, I had a look to the Apache Cassandra project (
http://cassandra.apache.org/), contributed by Facebook, and the Thrift API (
http://thrift.apache.org/). It seems to be an interesting way to design and
deploy distributed databases seamlessly accessible from python. Do anyone
have ex
Hi Jelle,
Interesting topic, this going to be a long thread!
The use of a python ORM is also the choice I would have done. In my mind,
there are two ways to model such a database:
- a "data centric" db: you store the result of the different operations you
ran (for instance a Point and a Cube);
-
I think that a distributed repository infrastructure is what's needed
for robust sharing of objects and model data. For sure, such
repositories would likely be based on a database-- but the repo would
need to expose crud ( create read update delete) functions via http,
so it is firwall and interne
22 matches
Mail list logo
