On Jan 20, 2008 1:26 PM, Stephen Waterbury <[EMAIL PROTECTED]> wrote:
> Christopher Armstrong wrote:
> > Hi Steve!
>
> Hi Chris!
>
> I saw that you were involved in Storm, which is part of the
> reason I decided to try it (in fact, I'm using your twisted-integration
> branch, though I haven't tried it out with twisted yet) -- at least I
> know that its twisted support will be good!
Glad to hear my influence is strong and far-reaching. But fyi, that
branch is Thomas Hervé's :)
> Actually, that wasn't exactly the problem I was referring to:
> SQL won't even let you *create* a column that is a *reserved*
> keyword (note that SQL has reserved keywords and non-reserved
> keywords -- the reserved ones are the ones you have to avoid).
> E.g.:
...
> >>> store.execute('CREATE TABLE thing '
> ... '(id INTEGER PRIMARY KEY, '
> ... ' authorization TEXT)')
> Traceback (most recent call last):
...
> psycopg2.ProgrammingError: syntax error at or near "authorization"
> LINE 1: CREATE TABLE thing (id INTEGER PRIMARY KEY, authorization T...
> ^
> -----------------------------------------------------------------------
>
> This is of course not Storm's fault at all: "authorization" is an
> SQL reserved keyword, so you can't have a column named
> "authorization", period.
Actually,
CREATE TABLE foo ("authorization" INTEGER);
works. If you create your schema with properly quoted column names,
you should be able to use storm with those column names and not have
any problems.
--
Christopher Armstrong
International Man of Twistery
http://radix.twistedmatrix.com/
http://twistedmatrix.com/
http://canonical.com/
--
storm mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/storm
