Closed phacops closed 9 years ago
+1
It would be nice if the project name would be used for the prefix, but instead, it seems to use the database name, which may be long (and which I can't do anything about!).
+1 I have the exact same issue, which prevents me from using this for local development.
I get "Incorrect database name" error, I think that for the same reason.
MySQL 5.6.17
+1 Same here.
sqlalchemy.exc.InternalError: (InternalError) (1059, u"Identifier name 'stellar_e2e_commerce_20140908142810_156566042c1a91f25d2e3f7bf4d41845_master' is too long") "CREATE DATABASE stellar_e2e_commerce_20140908142810_156566042c1a91f25d2e3f7bf4d41845_master CHARACTER SET = 'utf8'" ()
Any news on this? I also get the same error
sqlalchemy.exc.ProgrammingError: (ProgrammingError) (1102, u"Incorrect database name 'stellar_bxxxxxxxx_byyyyyy_cdaef62f069a8d0c1afef86f193e1590_master'") "CREATE DATABASE stellar_bxxxxxxxx_byyyyyy_cdaef62f069a8d0c1afef86f193e1590_master CHARACTER SET = 'utf8'" ()
Stellar generates a database name for the snapshot and the name is simply too long. It should be only 32 characters long.
Here is the backtrace: