Too bad :-)
Saves me a query.
Thanks
On Jul 8, 11:41 pm, Michael Bayer <[EMAIL PROTECTED]> wrote:
> right. like ive been saying all along, this bug is fixed in trunk and
> will be out in 0.3.9.
>
> On Jul 8, 2007, at 11:52 AM, mc wrote:
>
> > from sqlalchemy import *
> > db=create_engine('mysql:
On Jul 8, 5:47 pm, "Rick Morrison" <[EMAIL PROTECTED]> wrote:
> Also all this discussion leaves out the engine options. Right now a user has
> to make their own provisions for getting both Dialect and engine config
> options into a program using SA. either by hardcoding the options in the
> eng
On 7/8/07, Michael Bayer <[EMAIL PROTECTED]> wrote:
>
>
> thats ugly to me. if you know your DBAPI uses a certain argument,
> you should be able to just pass it through. similarly i dont want
> SA's args with some ugly prefix. prefixing is just a hack for
> something this fundamental.
Well th
On Jul 8, 2007, at 11:38 AM, klaus wrote:
>
> (Finally continuing this old thread.)
>
> The suggested fix does not seem to work. Here is an example:
>
> 1. To build the tables, create a schema test and run the following
> code:
>
cant reproduce. using trunk, with or without the patch, this scri
right. like ive been saying all along, this bug is fixed in trunk and
will be out in 0.3.9.
On Jul 8, 2007, at 11:52 AM, mc wrote:
> from sqlalchemy import *
> db=create_engine('mysql://user1:[EMAIL PROTECTED]/tests')
>
> create_s = """
> CREATE TABLE `users` (
> `user_name` varchar(16) NOT NU
On Jul 8, 2007, at 11:04 AM, Rick Morrison wrote:
> How about a simple scheme in which options meant for engine or
> dialect are prefixed with a tag that would differentiate them from
> other options that would be passed through to the DBAPI? Something
> like "sa-echo" or similar. Any othe
On Jul 8, 2007, at 3:32 PM, SamDonaldson wrote:
>
> Hello,
>
> I'm having trouble with the last_inserted_ids() function. I'm running
> an insert sql string as opposed to using the built in function. I
> thought I should be getting a resultproxy back and then I should be
> able to apply the las
On Jul 8, 2007, at 2:59 PM, alex bodnaru wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> hello,
>
> i was following this thread with interest, and found that
> last_inserted_ids returns the oid of the inserted record.
>
> can i portably retrieve a record by this oid?
>
no. it
Hello,
I'm having trouble with the last_inserted_ids() function. I'm running
an insert sql string as opposed to using the built in function. I
thought I should be getting a resultproxy back and then I should be
able to apply the last_inserted_ids function to get back the inserted
id. Why doesn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hello,
i was following this thread with interest, and found that
last_inserted_ids returns the oid of the inserted record.
can i portably retrieve a record by this oid?
alex
mc wrote:
> here is a working script, (need to change connection paramet
here is a working script, (need to change connection parameters , of
course).
When I run it the output is:
[1L]
[2L]
Excpected according to documentation:
['Jack']
['Jill']
###
from sqlalchemy import *
db=create_engine('mysql://user1:[EMAIL PROTECTED]/tests')
create_s = """
CREATE TABLE `users
(Finally continuing this old thread.)
The suggested fix does not seem to work. Here is an example:
1. To build the tables, create a schema test and run the following
code:
from sqlalchemy import *
metadata = BoundMetaData("...")
class Subject(object):
def __str__(self):
return "S
I like Paul's original idea, and although it may not work directly as
proposed, I'd like to see some kind of sanctioned way of getting engine and
dialect config data from a string-based external source, as the dburi
options provide for the DBAPI. It would be useful for the same reasons that
DBAPI o
13 matches
Mail list logo
