We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I have something like:
export const Entity = Class.create({ name: 'Entity', collection: Entities, typeField: 'type', fields: { uuid: { type: String, optional: true, }, published: { type: Boolean, default: true, },
and then numerous subclasses of that.
I was thinking of adding an index on type so I did like this:
export const Entity = Class.create({ name: 'Entity', collection: Entities, typeField: 'type', fields: { type: { type: String, index: "String" }, uuid: { type: String, optional: true, },
Does that sound reasonable? Is there any issue defining the field (and the index) like that even though I already specified the 'typeField' parameter?
Thanks
The text was updated successfully, but these errors were encountered:
@meecect you don't have to do that. Astronomy is already creating index for the type field for you https://github.com/jagi/meteor-astronomy/blob/v2/lib/modules/storage/hooks/apply_definition.js#L100
type
Sorry, something went wrong.
thank you, I was kinda assuming that it would, but thought I'd ask anyway.
No branches or pull requests
I have something like:
and then numerous subclasses of that.
I was thinking of adding an index on type so I did like this:
Does that sound reasonable? Is there any issue defining the field (and the index) like that even though I already specified the 'typeField' parameter?
Thanks
The text was updated successfully, but these errors were encountered: