Feeling dissatisfied with the options available in the current world
of graph databases (from what I can understand here:
http://en.wikipedia.org/wiki/Graph_database) I'm starting to think
that building a SQLAlchemy layer will be the easiest way to implement
the storage and retrieval of nodes and
On Jan 19, 2011, at 2:54 AM, Eric Lemoine wrote:
On Tue, Jan 18, 2011 at 11:33 PM, Michael Bayer
mike...@zzzcomputing.com wrote:
On Jan 18, 2011, at 4:47 PM, Eric Lemoine wrote:
On Tuesday, January 18, 2011, Eric Lemoine eric.lemo...@camptocamp.com
wrote:
Hi
Probably a very simple
HEllo Michael,
Thanks for your answer.
I tried order_by(func.monthfrom(datetime(2000, 1, 2, 0, 0, 0)))
but get the error:
global name func not defined.
I guess something must be put in front of it.
Any idea before I dig in.
My app works with Elixir.
Tnaks.
Frans.
--
You received
Thanks for responding,
I am using Postgresql 8.3.8 and Postgis 1.4. I have tried using both
DOUBLE_PRECISION and DOUBLE_PRECISION(asdecimal=True), with the same
errors.
thanks
On Jan 18, 3:50 pm, Michael Bayer mike...@zzzcomputing.com wrote:
Here's a tested example of DOUBLE_PRECISION using
I am assuming you ran the script that I sent previously, and it produced the
same errors.If this is not the case, please run that script. If it runs
without errors, then the solution is to ensure your program is passing
numerical values in the identical fashion as the test script, and that
Hi Folks,
I have been scratching my head over this one all day, so any advice
would be greatly appreciated!
I have a pretty simple join table setup like this:
foo foo_bar bar
---
id id_foo (unique) id
id_bar
Thanks again,
Your first script ran fine. I ended up doing something like this:
session.add(test_floats(id=2,max_pm10=Decimal(str(76945.283959)),
mean_pm10=Decimal(str(7683.27835
It was the only thing that eventually worked...
On Jan 19, 10:37 am, Michael Bayer
On Jan 19, 2011, at 12:52 PM, AgentOrange wrote:
Hi Folks,
I have been scratching my head over this one all day, so any advice
would be greatly appreciated!
I have a pretty simple join table setup like this:
foo foo_bar bar
Ran into an issue with having periods in column headings of SQL queries.
--
import sqlalchemy as sa
print(sa.__version__)
DB_URI = postgresql+psycopg2://test:test@localhost/testdb
engine = sa.create_engine (DB_URI)
qry = SELECT 1 AS test.this;
results = engine.execute(qry)
Hi ho,
Thanks for the swift reply!
Did you use uselist=False on foo.bar and the associationproxy? It would nice
if you could show some
code.http://www.sqlalchemy.org/docs/orm/extensions/associationproxy.html?h...
Yes I did. The code is more complicated as it has a bunch of other
stuff in
Sorry should have mentioned that I get this with 0.6.6 and 0.6.3
On 01/19/2011 10:27 AM, David Gardner wrote:
Ran into an issue with having periods in column headings of SQL queries.
--
import sqlalchemy as sa
print(sa.__version__)
DB_URI =
I think you'll find 0.7 doesn't do this anymore. SQLite has a behavior such
that column names get converted to tablename.colname in the case of selecting
from a UNION without explicit labels so we've always had a fixer for that. In
0.7 this fixer has been removed, and the sqlite dialect
Would you entertain the idea of a patch to disable this behavior when
SQLite isn't being used?
How soon do you want users to start testing of 0.7?
On 01/19/2011 11:05 AM, Michael Bayer wrote:
I think you'll find 0.7 doesn't do this anymore. SQLite has a
behavior such that column names get
On Jan 19, 2011, at 3:30 PM, David Gardner wrote:
Would you entertain the idea of a patch to disable this behavior when SQLite
isn't being used?
erm I'd rather not add a random flag into 0.6 which is well into maintenance
mode...
How soon do you want users to start testing of 0.7?
I
On Jan 19, 2011, at 1:29 PM, AgentOrange wrote:
Hi ho,
Thanks for the swift reply!
Did you use uselist=False on foo.bar and the associationproxy? It would nice
if you could show some
code.http://www.sqlalchemy.org/docs/orm/extensions/associationproxy.html?h...
Yes I did. The code
If I dont use autocommit:True option, it seems the driver will be in a
chained transaction mode and results in every single statement
(including selects) being run in a new transaction. This is not
desirable either.
Is there a way out ?
--
You received this message because you are subscribed
16 matches
Mail list logo