Between Operators keep find Operation lasting forever

Issue type:

[ x] bug report [ ] feature request [ ] documentation issue

Database system/driver:

[ ] cordova [ ] mongodb [ ] mssql [ ] mysql / mariadb [ ] oracle [ ] postgres [ ] cockroachdb [x] sqlite [ ] sqljs [ ] react-native [ ] expo

TypeORM version:

[ ] latest [ ] @next [x] github:cuibonobo/typeorm-package

Steps to reproduce or a small repository showing the problem:

1. Create a React-Native App and install this Typeorm, because default one not working with SQLite. Try to search with a where following a Between Statement like this:

const result = await repo.findAll(
                  {
                    where: {
                      leaveDate: Between(
                        formValue.from,
                        formValue.to,
                      ),
                    },
                    order: { lastname: "ASC" },
                  },
                );

1. Put this in an Async Function and put a statement after it, it will never gets executed.

I use the Custom Version because the default one never worked for me. Just keeped asking for react-native-sqlite-storage which was already installed!

[leonardofalk]

I think it’s not in the docs but the example:

https://github.com/typeorm/react-native-example/blob/master/src/App.tsx#L16

[imnotjames]

typeorm import will go to different things depending on how you’ve configured your bundler. metro SHOULD use the browser fields by default.

https://github.com/typeorm/typeorm/issues/6839#issuecomment-706673256

I replaced all references to typeorm/browser with just typeorm. EG import TypeORM from "typeorm";

I updated the metro.config.js to contain the following:

module.exports = {
  transformer: {
    getTransformOptions: async () => ({
        resolver: {
            resolverMainFields: ['browser', 'main']
        },
      transform: {
        experimentalImportSupport: false,
        inlineRequires: false,
      },
    }),
  },
};

Thing is, for the resolverMainFields - that’s the default. So it should be using that already.

Not saying this fixes your problem but it might help. I’ll still try to grab the repo down in the next few days if you haven’t resolved it by then 😃