The first dog table will generate a class and the second should be ignored. Which is not actually terrible behavior... but it should raise an error when it gets to the second table with the same name... giving a warning that there are two and that this will cause confusing results...
When the following pattern occurs:
somedatabase.dog otherdatabase.dog
The first dog table will generate a class and the second should be ignored. Which is not actually terrible behavior... but it should raise an error when it gets to the second table with the same name... giving a warning that there are two and that this will cause confusing results...