graflo.db.sql.introspect¶
Dialect-neutral classification of a relational schema into a graph.
Everything here derives from :class:~graflo.db.sql.provider.SqlMetadataProvider
and nothing else, which is the point: the heuristics that decide whether a table
is an entity or a relationship are about shape — keys, foreign keys, names —
and shape does not vary by engine. Only reading the catalogue does.
Lifted verbatim out of PostgresConnection, which still exposes these as
methods and now delegates here.
Attributes¶
logger = logging.getLogger(__name__)
module-attribute
¶
Classes¶
Functions:¶
build_raw_tables(provider, schema_name=None)
¶
Build raw table metadata for all tables in the schema.
Source code in graflo/db/sql/introspect.py
detect_edge_tables(provider, schema_name=None, vertex_table_names=None, *, default_schema=None)
¶
Detect edge-like tables in the schema.
Heuristic: Tables with 2 or more primary keys, or exactly 2 foreign keys, or names starting with 'rel_'. These represent relationships between entities.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
schema_name
|
str | None
|
Schema name. If None, uses 'public' or config schema_name. |
None
|
vertex_table_names
|
list[str] | None
|
Optional list of vertex table names for fuzzy matching. If None, will be inferred from detect_vertex_tables(). |
None
|
Returns:
| Type | Description |
|---|---|
list[EdgeTableInfo]
|
List of edge table information dictionaries with source_table and target_table |
Source code in graflo/db/sql/introspect.py
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 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 | |
detect_vertex_tables(provider, schema_name=None, *, default_schema=None)
¶
Detect vertex-like tables in the schema.
Heuristic: Tables with a primary key and descriptive columns (not just foreign keys). These represent entities.
Note: Tables identified as edge-like are excluded from vertex tables.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
schema_name
|
str | None
|
Schema name. If None, uses 'public' or config schema_name. |
None
|
Returns:
| Type | Description |
|---|---|
list[VertexTableInfo]
|
List of vertex table information dictionaries |
Source code in graflo/db/sql/introspect.py
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 | |
foreign_keys_in_column_order(fk_columns, all_columns)
¶
Order foreign-key rows by where their constraint sits in the table.
An edge table reads source, then target in the order its columns were
declared, and the first foreign key becomes the edge source. No catalog
promises that order: a query sorted by position within a constraint ties
across single-column constraints, and one sorted by constraint name puts
product_id before user_id. The table's own column order is the one
thing every provider reports the same way.
A constraint is placed by its earliest column; the rows of a composite key keep the order the provider gave them. Rows naming a column the table does not list sort last, in their original order.
Source code in graflo/db/sql/introspect.py
introspect_schema(provider, schema_name=None, include_raw_tables=False, *, default_schema=None)
¶
Introspect the database schema and return structured information.
This is the main method that analyzes the schema and returns information about vertex-like and edge-like tables.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
schema_name
|
str | None
|
Schema name. If None, uses 'public' or config schema_name. |
None
|
Returns:
| Type | Description |
|---|---|
SchemaIntrospectionResult
|
SchemaIntrospectionResult with vertex_tables, edge_tables, and schema_name |
Source code in graflo/db/sql/introspect.py
is_edge_like_table(table_name, pk_columns, fk_columns)
¶
Determine if a table is edge-like based on heuristics.
Heuristics: 1. Tables with 2 or more primary keys are likely edge tables 2. Tables with exactly 2 foreign keys are likely edge tables 3. Tables with names starting with 'rel_' are likely edge tables 4. Tables where primary key columns match foreign key columns are likely edge tables
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
table_name
|
str
|
Name of the table |
required |
pk_columns
|
list[str]
|
List of primary key column names |
required |
fk_columns
|
list[dict[str, Any]]
|
List of foreign key dictionaries |
required |
Returns:
| Type | Description |
|---|---|
bool
|
True if table appears to be edge-like, False otherwise |