Fixed this problem by using the standard DBServerInfo.
So it should be noted for inclusion of the GenericServerInfo to the
codebase that this functionality needs to be checked!
Kenny
On Feb 23, 4:53 pm, "Paul Rigor (gmail)" wrote:
> Hi Chris,
>
> The GenericServerInfo class adds a couple of thi
Here's our version of sqlgraph.py, from the 0.80 beta. He added a
class called GenericServerInfo (line 1806).
http://kmdaily.pastebin.com/f4cf21744
All I know that it does (for me) is it takes a parameter of a DB URI
instead of separate host, user, password parameters. I believe he
added it becau
On Feb 22, 2010, at 1:44 PM, Kenny Daily wrote:
> I'm looking into upgrading, but Paul added some class for added
> functionality to database connections that I'll have to get him to re-
> do - otherwise our connections are broken.
by the way, 0.8.0 has improvements to the handling of cursors an
On Feb 22, 2010, at 1:44 PM, Kenny Daily wrote:
> I'm looking into upgrading, but Paul added some class for added
> functionality to database connections that I'll have to get him to re-
> do - otherwise our connections are broken.
If this is a problem that isn't strictly specific to your databas
Indeed, I get back what you expect from the first test:
In [4]: G[G.sourceDB[1]]
Out[4]:
In [5]: G[G.sourceDB[1]].items()
Out[5]:
[(annot17186[0:2677],
)]
The second I get back integers, not objects:
In [6]: for a in G:
...: print a
...: break
...:
...:
1
I'm looking int
Hi Kenny,
this more or less fits what I said last time but doesn't shed much new light.
Out of curiosity, what happens if you take an Annotation object a1 from
resource1 and use it as a key to your SQLGraph, e.g. something like this:
a1 = resource1['key you know is in the mapping']
for a2, e in
Here's how I'm setting up the SQLGraph. I am also using the resource1,
resource2, and edges successfully for a ManyToManyRelation.
attrAlias = dict(source_id=opts.sourceid, target_id=opts.targetid,
edge_id=opts.edgeid)
edges = sqlgraph.SQLTable(opts.tablename, serverInfo=serverIn
