Closed gburu98-zz closed 8 years ago
Since Neo4J is schema-less, property types are unsupported, only constraints and indexes are supported.
thanks for responding, I have to remove the strings?
Yeah, you can only use
$label->unique()
$label->dropUnique()
$label->index()
$label->dropIndex()
After removing all the strings and enum you should be fine.
I worked perfectly and I can do migrations, but when i look for the label Users, find me "NeoEloquent Migration" and if I make another migration, I get another "NeoEloquent Migration", that is?
I'm sorry I'm not sure I got it :/. We are fairly active on slack https:// neo4j-users-slack-invite.herokuapp.com/ . Maybe we can talk a bit more over there?
On Fri, Sep 9, 2016 at 9:29 AM, Gastonb98 notifications@github.com wrote:
I worked perfectly and I can do migrations, but when i look for the label Users, find me "NeoEloquent Migration" and if I make another migration, I get another "NeoEloquent Migration", that is?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Vinelab/NeoEloquent/issues/171#issuecomment-245913038, or mute the thread https://github.com/notifications/unsubscribe-auth/ALGPKcV1S8xrooBoNa37wV9opzEBrcMVks5qoV9RgaJpZM4J5BBa .
Good day, I can not migrate a string field I printed the following error:
[Symfony\Component\Debug\Exception\FatalThrowableError] Call to undefined method Vinelab\NeoEloquent\Schema\Blueprint::string()