[sqlalchemy] Re: metadata reflecting all schemas

2008-11-30 Thread [EMAIL PROTECTED]

any sqlalchemy ways of retrieving a list of schemas?

On Nov 30, 1:23 pm, Michael Bayer [EMAIL PROTECTED] wrote:
 On Nov 29, 2008, at 6:05 PM, [EMAIL PROTECTED] wrote:



  Thanks Michael

  If its just a warning and its supposed to continue past it, Why
  doesn't it finish reflecting all the tables in all the schemas instead
  of a few tables in two schemas.

 that would be a different issue.   But I would note that
 metadata.reflect() only reflects one schema at a time, either the
 tables within the default schema, or those within the schema name
 which you specify.

  I think it retrieved all the tables in the first schema which i
  specified and followed the foreign keys to retrieve the metadata for
  the second tables.

 that's what it would do, yup.

  Any suggestions on how i can reflect a list of schemas or make it
  reflect all the schemas? it didn't like '%' as the schema name.

 you have to retreive the list of desired schemas manually, then call
 reflect() for each one.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
sqlalchemy group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en
-~--~~~~--~~--~--~---



[sqlalchemy] Re: metadata reflecting all schemas

2008-11-30 Thread Michael Bayer

not currently !  you'd have to issue the correct SQL for that database.

On Nov 30, 2008, at 4:18 AM, [EMAIL PROTECTED] wrote:


 any sqlalchemy ways of retrieving a list of schemas?

 On Nov 30, 1:23 pm, Michael Bayer [EMAIL PROTECTED] wrote:
 On Nov 29, 2008, at 6:05 PM, [EMAIL PROTECTED] wrote:



 Thanks Michael

 If its just a warning and its supposed to continue past it, Why
 doesn't it finish reflecting all the tables in all the schemas  
 instead
 of a few tables in two schemas.

 that would be a different issue.   But I would note that
 metadata.reflect() only reflects one schema at a time, either the
 tables within the default schema, or those within the schema name
 which you specify.

 I think it retrieved all the tables in the first schema which i
 specified and followed the foreign keys to retrieve the metadata for
 the second tables.

 that's what it would do, yup.

 Any suggestions on how i can reflect a list of schemas or make it
 reflect all the schemas? it didn't like '%' as the schema name.

 you have to retreive the list of desired schemas manually, then call
 reflect() for each one.
 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
sqlalchemy group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en
-~--~~~~--~~--~--~---



[sqlalchemy] Session.delete_all()

2008-11-30 Thread Eric Ongerth

IMO there should be a delete_all() convenience method on Session,
similar to what add_all() does, accepting an iterable as its
parameter.  Just to match up expected behavior with the existence of
add_all().

Side note: in the current API docs, add() is separated from add_all()
by an out-of-alphabetical-order listing of save_or_update().  I assume
in the forthcoming Sphinx semi-automation of docs, everything will be
strictly alphabetical...

Thanks,
Eric

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
sqlalchemy group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en
-~--~~~~--~~--~--~---