Hi Kenny, Yes, it's designed to support that, and the basic query functions are tested on SQLGraph for both mysql and sqlite in our standard test suite.
Without basic information like the stack dump showing what line the error occurred at, it's hard to give specific advice. Here is my best guess: - it looks like the AttributeError is coming not from GraphQuery but from SQLGraph. Are you sure your SQLGraph is properly set up to work completely? It looks like there is some confusion regarding the source or destination database objects: a database object is expected (e.g. as a key for a SQLGraph query) and as such is expected to have an 'id' attribute. According to the error message, instead of an object, a plain 'long' is getting passed. I hope that helps get you started. If you want to post a more detailed stack dump and basic info about your SQLGraph (the code that created it and populated it with data; the schemas of the source, dest and edge tables that it connects), we can try to help you figure this out. -- Chris -- You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to pygr-...@googlegroups.com. To unsubscribe from this group, send email to pygr-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en.
