date:20151009

Re: alembic_version in separate schema

2015-10-09 Thread Mike Bayer

see the version_table_schema parameter :

http://alembic.readthedocs.org/en/latest/api/runtime.html?highlight=version_table_schema#alembic.runtime.environment.EnvironmentContext.configure.params.version_table_schema



On 10/9/15 9:30 AM, wwwald wrote:
> Hi,
>
> Sorry if this is basic - I just started playing with Alembic.
> My current project will run on a shared PostgreSQL database, in which
> I only have permission to a specific schema, without writing
> permissions to "public". Can I configure Alembic to store the
> "alembic_version" table in that specific schema?
>
> Thanks in advance, 
> wwwald
> -- 
> You received this message because you are subscribed to the Google
> Groups "sqlalchemy-alembic" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to sqlalchemy-alembic+unsubscr...@googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sqlalchemy-alembic" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy-alembic+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[sqlalchemy] UniqueObject recipe with tables containing relationships and optional columns

2015-10-09 Thread Marten Jakobsen


Hi,

I'm using the UniqueObject recipe [1] for simple two column tables
and it works just fine, but what is the best way to use it with tables 
containing relationships?


I usually did:


mytime = Timestamp.as_unique(session, timestamp=value)
session.flush()
fingerprint = Fingerprint.as_unique(session, fingerprint='foo', 
ts_id=mytime.id)


Fingerprint class looks like this (timestamp is optional):

class Fingerprint(UniqueMixin, Base):
__tablename__ = 'fingerprint'
id = Column(mysql.MEDIUMINT(unsigned=True), primary_key=True)
fingerprint = Column(mysql.CHAR(16), nullable=False)
ts_id   = Column(mysql.SMALLINT(unsigned=True), 
ForeignKey('timestamp.id'))


timestamp  = relationship('Timestamp')

@classmethod
def unique_hash(cls, **kw):
return str(kw)

@classmethod
def unique_filter(cls, query, fingerprint, ts_id=None):
return query.filter(Fingerprint.fingerprint == fingerprint, 
Fingerprint.ts_id == ts_id)



to get rid of session.flush() I changed it to (which gave me a >100% 
speedup):



mytime = Timestamp.as_unique(session, timestamp=value)
fingerprint = Fingerprint.as_unique(session, fingerprint='foo', 
timestamp=mytime)


(also adjusting the unique_filter() to: ..., 
Fingerprint.timestamp==timestamp)


but it also shows this warning:

/usr/lib64/python2.7/site-packages/sqlalchemy/orm/relationships.py:1392: 
SAWarning: Got None for value of column timestamp.id; this is 
unsupported for a relationship comparison and will not currently produce 
an IS comparison (but may in a future release)

  "(but may in a future release)" % column)


Is it ok to use the latter way? (will it result in the same table 
content?)


thanks,
Marten



[1] 
https://bitbucket.org/zzzeek/sqlalchemy/wiki/UsageRecipes/UniqueObject


--
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.

Re: [sqlalchemy] UniqueObject recipe with tables containing relationships and optional columns

2015-10-09 Thread Mike Bayer



On 10/7/15 5:21 PM, Marten Jakobsen wrote:
> Hi,
>
> I'm using the UniqueObject recipe [1] for simple two column tables
> and it works just fine, but what is the best way to use it with tables
> containing relationships?
>
> I usually did:
>
>
> mytime = Timestamp.as_unique(session, timestamp=value)
> session.flush()
> fingerprint = Fingerprint.as_unique(session, fingerprint='foo',
> ts_id=mytime.id)
>
> Fingerprint class looks like this (timestamp is optional):
>
> class Fingerprint(UniqueMixin, Base):
> __tablename__ = 'fingerprint'
> id = Column(mysql.MEDIUMINT(unsigned=True), primary_key=True)
> fingerprint = Column(mysql.CHAR(16), nullable=False)
> ts_id   = Column(mysql.SMALLINT(unsigned=True),
> ForeignKey('timestamp.id'))
>
> timestamp  = relationship('Timestamp')

>
> @classmethod
> def unique_hash(cls, **kw):
> return str(kw)
>
> @classmethod
> def unique_filter(cls, query, fingerprint, ts_id=None):
> return query.filter(Fingerprint.fingerprint == fingerprint,
> Fingerprint.ts_id == ts_id)
>
>
> to get rid of session.flush() I changed it to (which gave me a >100%
> speedup):
>
>
> mytime = Timestamp.as_unique(session, timestamp=value)
> fingerprint = Fingerprint.as_unique(session, fingerprint='foo',
> timestamp=mytime)
>
> (also adjusting the unique_filter() to: ...,
> Fingerprint.timestamp==timestamp)
>
> but it also shows this warning:
>
> /usr/lib64/python2.7/site-packages/sqlalchemy/orm/relationships.py:1392:
> SAWarning: Got None for value of column timestamp.id; this is
> unsupported for a relationship comparison and will not currently
> produce an IS comparison (but may in a future release)
>   "(but may in a future release)" % column)
H.  I guess that *does* sort of work in that way, because the
fact that mytime has no ID means that we know Fingerprint has to be
created as well.I was going to suggest bundling the creation of
Fingerprint into Timestamp.  But actually, I'd just modify the recipe
here to see that when the incoming "mytime" object has no primary key
you skip the Query altogether that would normally be looking for
Fingerprint,  this would be inside of the _unique function.
 

>
>
> Is it ok to use the latter way? (will it result in the same table
> content?)
>
> thanks,
> Marten
>
>
>
> [1]
> https://bitbucket.org/zzzeek/sqlalchemy/wiki/UsageRecipes/UniqueObject
>


-- 
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.

[sqlalchemy] pgsql + jsonb + orm update = possible bug?

2015-10-09 Thread Richard Gerd Kuesters

Hello! I was working with a JSONB column in postgres and I noticed that 
no updates were issued when changing some inside value, so I have to 
issue "*flag_modified*" everytime I change my JSONB attribute. Here's a 
sample code that shows this:


   # -*- coding: utf-8 -*-

   from __future__ import unicode_literals


   from sqlalchemy import Column, Integer, create_engine
   from sqlalchemy.orm import Session
   from sqlalchemy.orm.attributes import flag_modified
   from sqlalchemy.ext.hybrid import hybrid_property
   from sqlalchemy.ext.declarative import declarative_base
   from sqlalchemy.dialects.postgresql import JSONB


   Base = declarative_base()


   class EntityA(Base):
__tablename__ = 'entity_a'

a_id = Column(Integer, primary_key=True)
a_value = Column(JSONB, nullable=False)


   class EntityB(Base):
__tablename__ = 'entity_b'

b_id = Column(Integer, primary_key=True)
_b_value = Column(JSONB, nullable=False)

@hybrid_property
def b_value(self):
return self._b_value

@b_value.setter
def b_value(self, value):
self._b_value = value


   class EntityC(Base):
__tablename__ = 'entity_c'

c_id = Column(Integer, primary_key=True)
_c_value = Column(JSONB, nullable=False)

@hybrid_property
def c_value(self):
return self._c_value

@c_value.setter
def c_value(self, value):
self._c_value = value
flag_modified(self, '_c_value')


   if __name__ == '__main__':
engine =
   create_engine('postgresql://test:test123@127.0.0.1/testing', echo=False)
Base.metadata.create_all(engine)
session = Session(engine)

# testing A, without hybrid property

a_test = EntityA()
a_test.a_value = dict(hello='world', test=1, enabled=True)

session.add(a_test)
session.commit()

print('EntityA, after insert:', a_test.a_value)

json_obj_a = a_test.a_value
json_obj_a['hello'] = 'foo'
a_test.a_value = json_obj_a

session.commit()

# assert a_test.a_value.get('hello') == 'foo'  # error
assert a_test.a_value.get('hello') == 'world'  # works

print('EntityA, after update:', a_test.a_value)

# testing B, with hybrid property and no flag_modified

b_test = EntityB()
b_test.b_value = dict(hello='world', test=1, enabled=True)

session.add(b_test)
session.commit()

print('EntityB, after insert:', b_test.b_value)

json_obj_b = b_test.b_value
json_obj_b['hello'] = 'bar'
b_test.b_value = json_obj_b

session.commit()

# assert b_test.b_value.get('hello') == 'bar'  # error
assert b_test.b_value.get('hello') == 'world'  # works

print('EntityB, after update:', b_test.b_value)

# testing C, with hybrid property and flag_modified

c_test = EntityC()
c_test.c_value = dict(hello='world', test=1, enabled=True)

session.add(c_test)
session.commit()

print('EntityC, after insert:', c_test.c_value)

json_obj_c = c_test.c_value
json_obj_c['hello'] = 'baz'
c_test.c_value = json_obj_c

session.commit()

assert c_test.c_value.get('hello') == 'baz'  # works
# assert c_test.c_value.get('hello') == 'world'  # error

print('EntityC, after update:', c_test.c_value)

# end test
session.close()

Base.metadata.drop_all(engine)


extra data, if needed:

   $ pip freeze
   psycopg2==2.6.1
   SQLAlchemy==1.0.8

   $ postgres --version
   postgres (PostgreSQL) 9.4.4

   $ python --version
   Python 2.7.10

   $ uname -a
   Linux marrow.polluxnet 4.2.3-1-ARCH #1 SMP PREEMPT Sat Oct 3
   18:52:50 CEST 2015 x86_64 GNU/Linux


thanks a lot, if any other information is needed, please let me know.


best regards,
richard.

--
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.
<>

Re: [sqlalchemy] pgsql + jsonb + orm update = possible bug?

2015-10-09 Thread Mike Bayer



On 10/9/15 8:33 AM, Richard Gerd Kuesters wrote:
> Hello! I was working with a JSONB column in postgres and I noticed
> that no updates were issued when changing some inside value, so I have
> to issue "*flag_modified*" everytime I change my JSONB attribute.
> Here's a sample code that shows this:

I see no usage of Mutable, which is required if you want to detect
updates within a JSON value.   See the notes on the JSON(B) types for this:

http://docs.sqlalchemy.org/en/rel_1_0/dialects/postgresql.html?highlight=jsonb#sqlalchemy.dialects.postgresql.JSONB

The |JSON|

type, when used with the SQLAlchemy ORM, does not detect in-place
mutations to the structure. In order to detect these, the
|sqlalchemy.ext.mutable|

extension must be used. This extension will allow “in-place” changes to
the datastructure to produce events which will be detected by the unit
of work. See the example at |HSTORE|

for a simple example involving a dictionary.



>
> # -*- coding: utf-8 -*-
>
> from __future__ import unicode_literals
>
>
> from sqlalchemy import Column, Integer, create_engine
> from sqlalchemy.orm import Session
> from sqlalchemy.orm.attributes import flag_modified
> from sqlalchemy.ext.hybrid import hybrid_property
> from sqlalchemy.ext.declarative import declarative_base
> from sqlalchemy.dialects.postgresql import JSONB
>
>
> Base = declarative_base()
>
>
> class EntityA(Base):
> __tablename__ = 'entity_a'
>
> a_id = Column(Integer, primary_key=True)
> a_value = Column(JSONB, nullable=False)
>
>
> class EntityB(Base):
> __tablename__ = 'entity_b'
>
> b_id = Column(Integer, primary_key=True)
> _b_value = Column(JSONB, nullable=False)
>
> @hybrid_property
> def b_value(self):
> return self._b_value
>
> @b_value.setter
> def b_value(self, value):
> self._b_value = value
>
>
> class EntityC(Base):
> __tablename__ = 'entity_c'
>
> c_id = Column(Integer, primary_key=True)
> _c_value = Column(JSONB, nullable=False)
>
> @hybrid_property
> def c_value(self):
> return self._c_value
>
> @c_value.setter
> def c_value(self, value):
> self._c_value = value
> flag_modified(self, '_c_value')
>
>
> if __name__ == '__main__':
> engine =
> create_engine('postgresql://test:test123@127.0.0.1/testing',
> echo=False)
> Base.metadata.create_all(engine)
> session = Session(engine)
>
> # testing A, without hybrid property
>
> a_test = EntityA()
> a_test.a_value = dict(hello='world', test=1, enabled=True)
>
> session.add(a_test)
> session.commit()
>
> print('EntityA, after insert:', a_test.a_value)
>
> json_obj_a = a_test.a_value
> json_obj_a['hello'] = 'foo'
> a_test.a_value = json_obj_a
>
> session.commit()
>
> # assert a_test.a_value.get('hello') == 'foo'  # error
> assert a_test.a_value.get('hello') == 'world'  # works
>
> print('EntityA, after update:', a_test.a_value)
>
> # testing B, with hybrid property and no flag_modified
>
> b_test = EntityB()
> b_test.b_value = dict(hello='world', test=1, enabled=True)
>
> session.add(b_test)
> session.commit()
>
> print('EntityB, after insert:', b_test.b_value)
>
> json_obj_b = b_test.b_value
> json_obj_b['hello'] = 'bar'
> b_test.b_value = json_obj_b
>
> session.commit()
>
> # assert b_test.b_value.get('hello') == 'bar'  # error
> assert b_test.b_value.get('hello') == 'world'  # works
>
> print('EntityB, after update:', b_test.b_value)
>
> # testing C, with hybrid property and flag_modified
>
> c_test = EntityC()
> c_test.c_value = dict(hello='world', test=1, enabled=True)
>
> session.add(c_test)
> session.commit()
>
> print('EntityC, after insert:', c_test.c_value)
>
> json_obj_c = c_test.c_value
> json_obj_c['hello'] = 'baz'
> c_test.c_value = json_obj_c
>
> session.commit()
>
> assert c_test.c_value.get('hello') == 'baz'  # works
> # assert c_test.c_value.get('hello') == 'world'  # error
>
> print('EntityC, after update:', c_test.c_value)
>
> # end test
> session.close()
>
> Base.metadata.drop_all(engine)
>
>
> extra data, if needed:
>
> $ pip freeze
> psycopg2==2.6.1
> SQLAlchemy==1.0.8
>
> $ postgres --version
> postgres (PostgreSQL)

alembic_version in separate schema

2015-10-09 Thread wwwald

Hi,

Sorry if this is basic - I just started playing with Alembic.
My current project will run on a shared PostgreSQL database, in which I 
only have permission to a specific schema, without writing permissions to 
"public". Can I configure Alembic to store the "alembic_version" table in 
that specific schema?

Thanks in advance, 
wwwald

-- 
You received this message because you are subscribed to the Google Groups 
"sqlalchemy-alembic" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy-alembic+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sqlalchemy] pgsql + jsonb + orm update = possible bug?

2015-10-09 Thread Richard Gerd Kuesters

thanks Mike! I'm glad I used a "?" in the subject :) I was thinking that 
something may be missing, so there it is ...


cheers,
richard.

On 10/09/2015 10:11 AM, Mike Bayer wrote:


I see no usage of Mutable, which is required if you want to detect 
updates within a JSON value. 


--
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.
<>

Re: alembic_version in separate schema

[sqlalchemy] UniqueObject recipe with tables containing relationships and optional columns

Re: [sqlalchemy] UniqueObject recipe with tables containing relationships and optional columns

[sqlalchemy] pgsql + jsonb + orm update = possible bug?

Re: [sqlalchemy] pgsql + jsonb + orm update = possible bug?

alembic_version in separate schema

Re: [sqlalchemy] pgsql + jsonb + orm update = possible bug?

7 matches

Site Navigation

Mail list logo

Footer information