1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68

#[macro_export]
/// Queries the database for the names of all tables, and calls
/// [`infer_table_from_schema!`](macro.infer_table_from_schema!.html) for each
/// one.
///
/// Attempting to use the `env!` or `dotenv!` macros here will not work due to limitations of
/// the Macros 1.1 system, but you can pass a string in the form `"env:SOME_ENV_VAR"` or
/// `"dotenv:SOME_ENV_VAR"` to achieve the same effect.
///
/// This macro can only be used in combination with the `diesel_codegen` or
/// `diesel_codegen_syntex` crates. It will not work on its own.
macro_rules! infer_schema {
    ($database_url: expr) => {
        #[derive(InferSchema)]
        #[options(database_url=$database_url)]
        struct _Dummy;
    }
}

#[macro_export]
/// Establishes a database connection at compile time, loads the schema information about a table's
/// columns, and invokes [`table!`](macro.table!.html) for you automatically.
///
/// Attempting to use the `env!` or `dotenv!` macros here will not work due to limitations of the
/// Macros 1.1 system, but you can pass a string in the form `"env:SOME_ENV_VAR"` or
/// `"dotenv:SOME_ENV_VAR"` to achieve the same effect.
///
/// At this time, the schema inference macros do not support types from third party crates, and
/// having any columns with a type not supported by the diesel core crate will result in a compiler
/// error (please [open an issue](https://github.com/diesel-rs/diesel/issues/new) if this happens
/// unexpectedly for a type listed in our docs.)
///
/// This macro can only be used in combination with the `diesel_codegen` or
/// `diesel_codegen_syntex` crates. It will not work on its own.
macro_rules! infer_table_from_schema {
    ($database_url: expr, $table_name: expr) => {
        #[derive(InferTableFromSchema)]
        #[options(database_url=$database_url, table_name=$table_name)]
        struct _Dummy;
    }
}

#[macro_export]
/// This macro will read your migrations at compile time, and embed a module you can use to execute
/// them at runtime without the migration files being present on the file system. This is useful if
/// you would like to use Diesel's migration infrastructure, but want to ship a single executable
/// file (such as for embedded applications). It can also be used to apply migrations to an in
/// memory database (Diesel does this for its own test suite).
///
/// You can optionally pass the path to the migrations directory to this macro. When left
/// unspecified, Diesel Codegen will search for the migrations directory in the same way that
/// Diesel CLI does. If specified, the path should be relative to the directory where `Cargo.toml`
/// resides.
///
/// This macro can only be used in combination with the `diesel_codegen` or
/// `diesel_codegen_syntex` crates. It will not work on its own.
macro_rules! embed_migrations {
    () => {
        #[derive(EmbedMigrations)]
        struct _Dummy;
    };

    ($migrations_path: expr) => {
        #[derive(EmbedMigrations)]
        #[options(migrations_path=$migrations_path)]
        struct _Dummy;
    }
}