"public.jtable"
> Column | Type | Modifiers | Storage | Stats target | Description
> +---+---+--+--+-
> data | jsonb | | extended | |
>
>
>
> maanantai 4. tammikuuta 2016 19.41.29 UTC+2 Jo
ta @>
> %(data_1)s'] [parameters: {'data_1': 'third'}]
>
>
> torstai 31. joulukuuta 2015 16.11.47 UTC+2 Jon Rosebaugh kirjoitti:
> >
> > Your SQL itself isn't going to work; there's no 'item' column in your
> > select statement. You should read
> > http://www.p
Your SQL itself isn't going to work; there's no 'item' column in your
select statement. You should read
http://www.postgresql.org/docs/9.4/interactive/functions-json.html to
see what operators you have. (I think you want '@>', not LIKE.)
In SQLAlchemy, this would be done as
I think you might want to use the lightweight sqlalchemy.column()
(lowercase!) expression; UniqueConstraint(sa.column('data',
JSON)['email']) might work.
On 12/30/15 5:58 PM, Andrew Muro wrote:
(SQLAlchemy 1.0.11)
I'm trying to figure out how to define a unique constraint from within
the
Sure, but declarative classes have a table.
MyModel.__table__.info['exclude_from_autogen']=True
(you'll probably want to write a class decorator that sets this,
actually.)
On Wed, Nov 18, 2015, at 02:59 AM, Michal Petrucha wrote:
> On Tue, Nov 17, 2015 at 11:26:41AM -0500, Jon Rosebaugh wr
I would definitely agree using postgres in both dev and prod is the way
to go here; sqlite behaves sufficiently differently, particularly around
DDL.
At Axial we previously had multiple databases in concurrent use, with
migrations operating on both databases at once. We modified env.py's
You can configure an include_object() function which can inspect the
model and decide whether or not to include the model in autogenerated
migrations:
http://alembic.readthedocs.org/en/latest/api/runtime.html#alembic.runtime.environment.EnvironmentContext.configure.params.include_object
Then you
it, func.row_to_json(literal_column(’s’)).
On Oct 2, 2014, at 11:54 PM, Jon Rosebaugh cha...@gmail.com javascript:
wrote:
I'm having some trouble with the Postgresql function row_to_json. It's
possible to use it on an entire table to turn each row from the table into
a JSON object, like
I'm having some trouble with the Postgresql function row_to_json. It's
possible to use it on an entire table to turn each row from the table into
a JSON object, like select row_to_json(t) as j from some_table as t. You
can also use a subselect, and that's where the trouble lies.
I want to
At my workplace, we use Alembic to handle migrations, but we
frequently have minor issues like forgetting to downgrade to the most
recent common migration before switching git branches, or not noticing
that a branch has migrations to be run when checking it out. This
causes a bit of aggravation.
I'm trying to implement support for Postgres's composite types, which
essentially let you make a type which is a struct of other types. This
involves several kinds of functionality:
* Psycopg2 maps composite types as namedtuples. However,
the register_composite() function has to be called for
The url I've been using for the 0.8 docs
(http://docs.sqlalchemy.org/en/rel_0_8/) now goes to a page listing 0.9
docs. There doesn't seem to be any way to get at 0.8's docs from the
website.
--
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To
checking out
master. I'm not sure how to fix this at the moment.
On Jun 2, 2013, at 8:34 PM, Jon Rosebaugh cha...@gmail.com javascript:
wrote:
The url I've been using for the 0.8 docs (
http://docs.sqlalchemy.org/en/rel_0_8/) now goes to a page listing 0.9
docs. There doesn't seem
On Jan 7, 2008 2:20 PM, Michael Bayer [EMAIL PROTECTED] wrote:
0.4.2b
--
- sql
- changed name of TEXT to Text since its a generic type; TEXT
name is
deprecated until 0.5. The upgrading behavior of String to Text
when no length is present is also deprecated until
14 matches
Mail list logo
