Forum https://discourse.hanamirb.org – Code of Conduct http://hanamirb.org/community/#code-of-conduct
adam12 on pg-env-variables
Revert "Log ENV" This reverts … Never prompt for password in Gi… (compare)
adam12 on pg-env-variables
Log ENV (compare)
adam12 on pg-env-variables
Pass environment variables to e… (compare)
adam12 on pg-env-variables
fixup! Pass env to system in po… (compare)
adam12 on pg-env-variables
Pass env to system in postgresq… Remove manual PGPASSWORD settin… Call postgresql command with en… (compare)
depfu[bot] on update
Update rubocop to version 1.11.0 (compare)
depfu[bot] on update
Enumerator.produce
and I'm loving it. Why isn't there more noise about this absolutely fantastic (experimental) addition to Ruby? Check it out
Ah yes I saw that - I was interested as to that - a note there
Custom schema takes precedence over automatic schema. If we use custom schema, we need to manually add all the new columns from the corresponding SQL database table.
Which is unclear to me. If I use custom schema attributes, does it completely override the other columns? Or can I use both - sometimes its just nice to have some overlying business logic validations to ensure bad data cannot enter the persistence layer at that boundary
Sequel::InvalidValue at
ArgumentError: no time information in ""
def call(params)
@page = PageRepository.by_title(params[:id])
if @page.nil?
@page = Page.new(title: params[:id])
self.body = Web::Views::Pages::NotFound.render(exposures)
end
end