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
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
//! # postgres-mapper
//!
//! `postgres-mapper` is a proc-macro designed to make mapping from postgresql
//! tables to structs simple.
//!
//! ### Why?
//!
//! It can be frustrating to write a lot of boilerplate and, ultimately, duplicated
//! code for mapping from postgres Rows into structs.
//!
//! For example, this might be what someone would normally write:
//!
//! ```rust
//! extern crate postgres;
//!
//! use postgres::rows::Row;
//!
//! pub struct User {
//! pub id: i64,
//! pub name: String,
//! pub email: Option<String>,
//! }
//!
//! impl From<Row> for User {
//! fn from(row: Row) -> Self {
//! Self {
//! id: row.get("id"),
//! name: row.get("name"),
//! email: row.get("email"),
//! }
//! }
//! }
//!
//! // code to execute a query here and get back a row
//! let user = User::from(row); // this can panic
//! ```
//!
//! This becomes worse when manually implementating using the non-panicking
//! `get_opt` method variant.
//!
//! Using this crate, the boilerplate is removed, and panicking and non-panicking
//! implementations are derived:
//!
//! ```rust
//! #[macro_use] extern crate postgres_mapper_derive;
//! extern crate postgres_mapper;
//!
//! use postgres_mapper::FromPostgresRow;
//!
//! #[derive(PostgresMapper)]
//! pub struct User {
//! pub id: i64,
//! pub name: String,
//! pub email: Option<String>,
//! }
//!
//! // code to execute a query here and get back a row
//!
//! // `postgres_mapper::FromPostgresRow`'s methods do not panic and return a Result
//! let user = User::from_postgres_row(row)?;
//! ```
//!
//! ### The two crates
//!
//! This repository contains two crates: `postgres-mapper` which contains an `Error`
//! enum and traits for converting from a `postgres` or `tokio-postgres` `Row`
//! without panicking, and `postgres-mapper-derive` which contains the proc-macro.
//!
//! `postgres-mapper-derive` has 3 features that can be enabled (where T is the
//! struct being derived with the provided `PostgresMapper` proc-macro):
//!
//! - `postgres-support`, which derives
//! `impl<'a> From<::postgres::rows::Row<'a>> for T` and
//! `impl<'a> From<&'a ::postgres::Row<'a>> for T` implementations
//! - `tokio-postgres-support`, which derives
//! `impl From<::tokio_postgres::rows::Row> for T` and
//! `impl From<&::tokio_postgres::rows::Row> for T` implementations
//! - `postgres-mapper` which, for each of the above features, implements
//! `postgres-mapper`'s `FromPostgresRow` and/or `FromTokioPostgresRow` traits
//!
//! `postgres-mapper` has two features, `postgres-support` and
//! `tokio-postgres-support`. When one is enabled in `postgres-mapper-derive`, it
//! must also be enabled in `postgres-mapper`.
//!
//! ### Installation
//!
//! The above might be confusing, so here's an example where `tokio-postgres` is
//! enabled in both crates:
//!
//! Add the following to your `Cargo.toml`:
//!
//! ```toml
//! [dependencies.postgres-mapper]
//! features = ["tokio-postgres-support"]
//! version = "0.1"
//!
//! [dependencies.postgres-mapper-derive]
//! features = ["postgres-mapper", "tokio-postgres-support"]
//! version = "0.1"
//! ```
//!
//! This will derive implementations for converting from owned and referenced
//! `tokio-postgres::rows::Row`s, as well as implementing `postgres-mapper`'s
//! `FromTokioPostgresRow` trait for non-panicking conversions.
extern crate postgres;
extern crate tokio_postgres;
use Error as PostgresError;
use Error as StdError;
use ;
use Row as PostgresRow;
use Row as TokioRow;
/// Trait containing various methods for converting from a postgres Row to a
/// mapped type.
///
/// When using the `postgres_mapper_derive` crate's `PostgresMapper` proc-macro,
/// this will automatically be implemented on types.
///
/// The [`from_postgres_row`] method exists for consuming a `Row` - useful for
/// iterator mapping - while [`from_postgres_row_ref`] exists for borrowing a
/// `Row`.
/// Trait containing various methods for converting from a `tokio-postgres` Row
/// to a mapped type.
///
/// When using the `postgres_mapper_derive` crate's `PostgresMapper` proc-macro,
/// this will automatically be implemented on types.
///
/// The [`from_tokio_postgres_row`] method exists for consuming a `Row` - useful
/// for iterator mapping - while [`from_postgres_row_ref`] exists for borrowing
/// a `Row`.
/// General error type returned throughout the library.