Closed bheemreddy181-zz closed 5 years ago
Could you please detail on how you would proceeed ? Some sql
bases use cases would help a lot, I'd like to be really sure to understand it.
My first feeling is that it's a very good idea, timezones can be a mess :+1:
What could be very cool would to
sql
, get the full detailed DDLCOPY
)criticity
and think about a nicely understandable message for end usersBtw, why ot putting an avatar for yourself on GH ? :smile_cat:
Typically my approach would be like find any column with Timestamp Type and Error out Saying - Timestamp without time zone (timestamp) is not a permitted data type. Use timestamp with time zone (timestamptz)
, Juts one additional util should be for this.
Hmmm, that becomes really interesting ! We'll have to take a look at how we get this metadata in schemacrawler.
What do you mean by metadata? Can you please elaborate? below is the sample report post-implementation.
You mean the lint has been implemented :question: :exclamation: :heavy_heart_exclamation: :heart_eyes:
PR will be out Soon :-p
looks like you are crazy too bro' :laughing: :rocket:
Thanks @bheemreddy181 for your contribution 👍
When can I expect this to get released ?
@mbarre : if you are ok with this, I can release today ?
This is something specific to Date Type Columns - I see that Postgres supports different Date types but it's is a pain for DBA when migrating data to different databases when they come across timestamp type column without timezone.
I would like to create a PR for this and keep this disabled -setting the flag to false, meanwhile, I would like to hear from you people whether this lint makes sense.
@adriens if it makes sense, can you label this with [enhancement]