sailsbot
commented
4 years ago @LouAdrien Thanks for posting! We'll take a look as soon as possible.
In the mean time, there are a few ways you can help speed things along:
- look for a workaround. (Even if it's just temporary, sharing your solution can save someone else a lot of time and effort.)
- tell us why this issue is important to you and your team. What are you trying to accomplish? (Submissions with a little bit of human context tend to be easier to understand and faster to resolve.)
- make sure you've provided clear instructions on how to reproduce the bug from a clean install.
- double-check that you've provided all of the requested version and dependency information. (Some of this info might seem irrelevant at first, like which database adapter you're using, but we ask that you include it anyway. Oftentimes an issue is caused by a confluence of unexpected factors, and it can save everybody a ton of time to know all the details up front.)
- read the code of conduct.
- if appropriate, ask your business to sponsor your issue. (Open source is our passion, and our core maintainers volunteer many of their nights and weekends working on Sails. But you only get so many nights and weekends in life, and stuff gets done a lot faster when you can work on it during normal daylight hours.)
- let us know if you are using a 3rd party plugin; whether that's a database adapter, a non-standard view engine, or any other dependency maintained by someone other than our core team. (Besides the name of the 3rd party package, it helps to include the exact version you're using. If you're unsure, check out this list of all the core packages we maintain.)
Please remember: never post in a public forum if you believe you've found a genuine security vulnerability. Instead, disclose it responsibly.
For help with questions about Sails, click here.
eashaw
Node version: Sails version (sails): 1.2.3 ORM hook version (sails-hook-orm): Sockets hook version (sails-hook-sockets): Organics hook version (sails-hook-organics): Grunt hook version (sails-hook-grunt): Uploads hook version (sails-hook-uploads): DB adapter & version (e.g. sails-mysql@5.55.5): Skipper adapter & version (e.g. skipper-s3@5.55.5): "sails-mongo": "^1.0.1",
Using a criteria when populating association raise the warning below. Mongobd does support native join ($lookup). Would it be possible to use it to implement the missing feature?
Warning: Attempting to populatetutorialswith the specified subcriteria, but this MAY NOT BE SAFE, depending on the number of records stored in your models. Since this association does not support optimized populates (i.e. it spans multiple datastores, or uses an adapter that does not support native joins), it is not a good idea to populate it along with a subcriteria that useslimit,skip, and/orsort`-- at least not in a production environment.This is because, to satisfy the specified
limit/skip/sort, many additional records may need to be fetched along the way -- perhaps enough of them to overflow RAM on your server.If you are just using sails-disk during development, or are certain this is not a problem based on your application's requirements, then you can safely ignore this message. But otherwise, to overcome this, either (A) remove or change this subcriteria and approach this query a different way (such as multiple separate queries or a native query), or (B) configure all involved models to use the same datastore, and/or switch to an adapter like sails-mysql or sails-postgresql that supports native joins. [?] See https://sailsjs.com/support for help.`