to_sql¶
- Features.to_sql(targets: bool = True, subfeatures: bool = True, dialect: str = 'sqlite3', schema: Optional[str] = None, nchar_categorical: int = 128, nchar_join_key: int = 128, nchar_text: int = 4096, size_threshold: Optional[int] = 50000) SQLCode[source]¶
Returns SQL statements visualizing the features.
- Args:
- targets (boolean):
Whether you want to include the target columns in the main table.
- subfeatures (boolean):
Whether you want to include the code for the subfeatures of a snowflake schema.
- dialect (string):
The SQL dialect to use. Must be from
dialect. Please note that not all dialects are supported in the getML community edition.- schema (string, optional):
The schema in which to wrap all generated tables and indices. None for no schema. Not applicable to all dialects. For the BigQuery and MySQL dialects, the schema is identical to the database ID.
- nchar_categorical (int):
The maximum number of characters used in the VARCHAR for categorical columns. Not applicable to all dialects.
- nchar_join_key (int):
The maximum number of characters used in the VARCHAR for join keys. Not applicable to all dialects.
- nchar_text (int):
The maximum number of characters used in the VARCHAR for text columns. Not applicable to all dialects.
- size_threshold (int, optional):
The maximum number of characters to display in a single feature. Displaying extremely complicated features can crash your iPython notebook or lead to unexpectedly high memory consumption, which is why a reasonable upper limit is advantageous. Set to None for no upper limit.
Examples:
my_pipeline.features.to_sql()